Create Redmine issues with AI: turn screenshots into complete issues

A screenshot captures a problem, but it rarely explains everything a developer needs. Someone still has to describe the page, reproduce the behavior, specify the expected result, and choose a project and assignee. With many findings, organizing issues can take longer than capturing the evidence.

Bunny Redmine reads supplied screenshots and text, organizes them using your team's rules, and uses authorized Redmine tools to create issues. Instead of stopping at text you must copy and paste, it can put the work into the system your team uses to assign and track it.

1. Supply the screenshot and explain the action

For example: “After signing in, saving customer details shows this error. Create a defect in the customer portal project.” Add the browser, environment, version, and account role if known. The screenshot shows the visible state; your explanation supplies the sequence and context.

Information absent from the input should not be invented. Configure the Prompt to ask for missing reproduction details or list them as questions in the issue.

2. Prepare information someone can act on

Bunny can apply an issue template covering the following:

• A specific subject describing the affected function and failure.
• Steps to reproduce, starting from a known page or state.
• Actual and expected behavior.
• Supplied environment details and attachments.
• Acceptance criteria describing observable results.
• Missing information that still needs confirmation.

“Save is broken” might become “Saving customer details returns an error and changes are not retained.” A useful acceptance criterion is “Reopening the page shows the saved changes,” not simply “The feature works.” This is an illustrative example, not a reported customer result.

3. Check existing issues before creating another

Bunny can search permitted issues for related reports. It can add evidence to an existing issue, create a new one, or organize related work using issue relations and subtasks. An uncertain match should be flagged for review rather than treated as a reason to delete or close work.

Projects, trackers, priorities, versions, and assignees follow the deployment's configuration and account permissions. Unknown deadlines do not need to be invented to fill every field.

4. Create the issue and keep follow-up in Redmine

Within authorized tools and account permissions, Bunny can create an issue, attach files, assign an owner, and add comments. Your Prompt can require draft approval or allow well-defined work to be created directly. Larger tasks can be split into parent and child issues.

Subsequent questions, progress, and verification results can stay with the issue. Scheduled work can check stale items and request updates. Final closure follows your team's confirmation rules.

Start with one template

Choose one project and a common issue type. Define required information, tools, assignment rules, and approval points. Test representative inputs for accuracy and evidence completeness before expanding to requirements or customer feedback.

See the official Redmine issue documentation for native issue relations and subtasks. Bunny operations depend on the deployed configuration and permissions.