Jira Concepts - Issues
Jira tracks issues, which can be bugs, feature requests, or any other tasks you want to track.
Each issue has a variety of associated information including:
- the issue type
- a summary
- a description of the issue
- the project which the issue belongs to
- components within a project which are associated with this issue
- versions of the project which are affected by this issue
- versions of the project which will resolve the issue
- the environment in which it occurs
- a priority for being fixed
- an assigned developer to work on the task
- a reporter - the user who entered the issue into the system
- the current status of the issue
- a full history log of all field changes that have occurred
- a comment trail added by users
- if the issue is resolved - the resolution
Issue Types
Jira can be used to track many different types of issues. The currently defined issue types are listed below. In addition, you can add more in the administration section.
For Regular Issues
- Bug
- A problem which impairs or prevents the functions of the product.
- New Feature
- A new feature of the product, which has yet to be developed.
- Task
- A task that needs to be done.
- Improvement
- An improvement or enhancement to an existing feature or task.
- Story
- Created by Jira Software - do not edit or delete. Issue type for a user story.
- Design
- For design, UI/UX, graphical, etc. non-code tickets.
- Mini Version
- Epic
- Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
For Sub-Task Issues
- Sub-task
- The sub-task of the issue
- Sub-Improvement
- Sub-New Feature
Priority Levels
An issue has a priority level which indicates its importance. The currently defined priorities are listed below. In addition, you can add more priority levels in the administration section.
- High
- Major loss of function.
- Normal
- Loss of function, or other unwanted behavior.
- Low
- Minor loss of function, or other problem where easy workaround is present.
Statuses
Status Categories
Helps identify where an issue is in its lifecycle.
Issues move from To Do to In Progress when work starts on them, and later move to Done when all work is complete.
- Done
-
Represents anything for which work has been completed
- In Progress
-
Represents anything in the process of being worked on
- No Category
-
A category is yet to be set for this status
- To Do
-
Represents anything new
Issue Statuses
Each issue has a status, which indicates the stage of the issue. In the default workflow, issues start as being Open, progressing to In Progress, Resolved and then Closed. Other workflows may have other status transitions.
- Open
- The issue is open and ready for the assignee to start work on it.
- In Progress
- This issue is being actively worked on at the moment by the assignee.
- Reopened
- This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
- Review Submitted
- A review has been submitted and is waiting peer review before the issue can be closed.
- Closed
- The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
- Decision Required
- The issue requires a decision to be made before the developer is able to move forward and start/continue work.
- RFC Required
- This issue requires additional planning and/or community involvement before it can be implemented.
- In Beta Testing
- Currently being user tested at beta.musicbrainz.org
- RFC Sent
- An RFC has been sent to the style list.
- RFV Sent
- An RFV has been sent to the style list.
- Blocked
- Progress cannot continue on the issue until another ticket is resolved.
- Release Pending
- The code has been merged but not yet released.
- In Development Branch
- The code has been merged to the development branch (usually master), but won't enter beta until the next release cycle.
- To Do
- In Review
- Done
- Under Review
- Approved
- Cancelled
- Rejected
- Mockup Required
- This ticket needs a mockup to progress.
- Mockup Submitted
- A mockup has been submitted, pending review.
- Implementation Requested
- The issue needs to be implemented in the code of MusicBrainz Server. A new MBS issue should be created with a dependency link to the current STYLE issue.
- Documentation Required
- The issue is implemented in the code of MusicBrainz Server, that is the linked MBS issue should be closed, but the WikiDoc needs to be updated and transcluded.
Resolutions
An issue can be resolved in many ways, only one of them being "Fixed". The defined resolutions are listed below. You can add more in the administration section.
- Fixed
- A fix for this issue is checked into the tree and tested.
- Won't Fix
- The problem described is an issue which will never be fixed.
- Duplicate
- The problem is a duplicate of an existing issue.
- Incomplete
- The problem is not completely described.
- Cannot Reproduce
- All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue.
- Invalid
- RFC Required
- This suggestion is a won't fix until a proposal sent to the style list has passed.
- Done
- Work has been completed on this issue.
- Won't Do
- This issue won't be actioned.