Redmine Issues¶
Issues come in several varieties. For each issue, you describe what is being tracked, who is assigned to work on it, and set its current state. The available issue varieties include:
Issue Type | Purpose |
Action Item | Track generic action items. |
Bug | Track problems being fixed in existing product. |
Feature | Track new features being developed for a product. |
Support | Track support issues, may just be questions. |
Enhancement | Track new enhancement requests (not yet under development). |
The general workflow in terms of issue states for the issues is shown below. The workflow is simplified in that it shows the conceptual flow. The actual flow could be a little different. Some states might be skipped or repeated but the conceptual flow is useful for setting expectations.
If an issue is unassigned, it is owned by the Project Manager. When an issue is explicitly assigned to an individual, there is an expectation that the issue should be worked on. The issue status and comments should clearly identify what the expected work is. The work could be answering questions or doing development.
The different issue statuses are as follows:
Status | Description | Assigned/Unassigned |
New | Initial state for an issue. | Unassigned or Project Manager |
Investigation | Bug analysis, feature clarification. Answering specific questions. | Assigned |
On Hold | Issue is not being worked on. Waiting for a trigger to continue further activity | Project Manager |
In Progress | Issue is being worked on. | Assigned |
Integration | Issue is being tested or packaged into a deliverable. | Assigned |
Resolved | Development is complete and available, pending verification. | Assigned for verification |
Feedback | Resolution or rejection is not accepted because of stated reasons. | Project Manager |
Rejected | Issue has been rejected for stated reasons, pending agreement | Assigned |
Closed | Resolved issue has been verified. | -- |
Closed-Rejected | Rejected issue has been agreed to. | -- |
Go to top