Your Redmine runs on your own server, and so does your vibe-code agent — the AI assistant in the Open WebUI chat that can read Redmine’s files, query its database, run rake commands, and restart services. Instead of clicking through admin screens, you describe the job in plain language and the agent does it. Here are ten everyday jobs worth delegating first.
1. Triage the unassigned backlog
Open issues with nobody assigned are where requests go to die. Ask the agent to list every open issue with no assignee, grouped by project and priority, and to flag the ones that haven’t been updated in weeks. It can run a read-only SQL query against the issues table, show you the list, and only then make the bulk changes you approve — assignments, target versions, or closures. Show me every open issue in the Warehouse project assigned to nobody, ordered by priority, and flag any that haven’t been updated in 30 days.
2. Get a Monday morning digest
You shouldn’t have to click through five projects to know what happened last week. The agent can build a scheduled summary: issues opened, closed, and still aging, hours logged per project, and versions slipping past their due dates. Because Redmine tracks journals on every issue, the underlying numbers are already there — the agent just aggregates them. Have the digest emailed to you, or posted as a News item in Redmine so the whole team sees the same numbers. Every Monday at 8:00, email me a digest of issues opened and closed last week across all active projects, plus the five oldest open bugs.
3. Log time without opening a form
Redmine’s time tracking is only as good as the entries people actually file, and forms are exactly where logging breaks down. When you finish a piece of work, just tell the agent what you did. It creates the time entry on the issue with the right activity category and a proper comment, then confirms it shows up on the issue’s Spent time tab. Add 1.5 hours to issue #248, activity Development, comment ‘reviewed the DB migration script’.
4. Keep versions honest
A version with a due date in the past and open issues attached is a roadmap lie. Ask for a quick health check: which versions are overdue, what percentage of their issues are closed, and which blockers are pinned to upcoming releases. From that list you can push due dates or move whole batches of issues to the next version in one pass. List every version past its due date that still has open issues, then move the open issues in version 2.4 to version 2.5.
5. Build a meeting-ready Gantt view
Before a status call, you want the right filtered view without ten minutes of clicking through query builders. The agent can create a saved custom query — open issues for a specific version or assignee, grouped by tracker or category, sorted by due date — and mark it public so the whole team sees it. It shows up in the sidebar on the issue list, Gantt, and calendar, so it is one click away every time instead of a filter you rebuild before each meeting. The agent can also make a private variant for your own daily queue. Create a public query called ‘Q4 roadmap’ in the Webshop project that shows open issues for version 4.0, grouped by tracker, sorted by due date.
6. Close duplicate tickets in bulk
Support queues fill up with the same password-reset or sync-error ticket filed over and over. The agent can search subjects and descriptions, cluster the likely duplicates, and close them in one pass with a comment pointing at the canonical issue. Review the cluster list before it pulls the trigger so nothing real gets swept up. Find all support tickets from the last 60 days mentioning ‘password reset’, close them as duplicates of #512, and add a comment on each pointing to it.
7. Onboard a new teammate
Creating a user, adding them to the right projects with the right role, subscribing them to key issues, and confirming they can’t see what they shouldn’t is normally five admin screens. The agent can do it as one job and report back exactly which permissions apply, including what the anonymous and non-member roles would let them see. It can also set the password policy, flag the account for activation, and send Jane a short getting-started note pointing at the wiki. Create a user for jane@example.com, add her to the Webshop project with the Developer role, subscribe her to issues #101 through #110, and verify she has no access to the Finance project.
8. Turn meeting notes into issues
You paste raw notes; Redmine gets structured work items. The agent drafts issues with subjects, descriptions, trackers, target versions, and assignees, shows you the draft list, and only creates them once you approve. No more copying bullet points out of a doc and losing who promised what. Create issues in the Redesign project from these notes: three items, all tracker Feature, target version 4.0, and assign the API one to Marcus.
9. Prune stale content
Wikis and news sections rot quietly: orphaned wiki pages, announcements for releases two years old, forums nobody moderates. The agent can inventory content with no recent updates and no incoming links, then draft an archive plan for your review instead of deleting anything behind your back. List wiki pages in the IT project with no updates in 18 months and no links to them, and draft an archive plan.
10. Ask the database directly
Some questions are awkward or impossible in the UI: hours logged in a date range broken down by user, issues that were reopened more than twice, projects with zero activity in a year. The agent writes a read-only SQL query against the Redmine database and hands you back a clean table, run through a database user that cannot modify anything. Ask for the same numbers next month and it can turn the query into a repeatable report. How many hours were logged on the Warehouse project in September, broken down by user?
Start with read-only requests and graduate to bulk changes once you trust how the agent verifies its work. Every command runs on your server, against your data. See Redmine on OpenSysLab.
