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
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
- New Feature
- A new feature of the product, which has yet to be developed.
- An improvement or enhancement to an existing feature or task.
- A problem which impairs or prevents the functions of the product.
- A big user story that needs to be broken down. Created by JIRA Software - do not edit or delete.
- A user story. Created by JIRA Software - do not edit or delete.
- A task that needs to be done.
- Unforeseen story
- Contract support
- Work incident
- Plan request
- Account management
For Sub-Task Issues
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.
- Blocks development and/or testing work, production could not run.
- Crashes, loss of data, severe memory leak.
- Major loss of function.
- Minor loss of function, or other problem where easy workaround is present.
- Cosmetic problem like misspelt words or misaligned text.
- Solve within 24 hour
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.
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
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.
- Waiting for answer
- 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.
- This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
- Ready for deploy
- The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
- Source code has been committed, and JIRA is waiting for the code to be built before moving to the next status.
- Build Broken
- The source code committed for this issue has possibly broken the build.
- To do
- Code review & devtest
- More votes required
- In deze fase wordt een plan gemaakt voor het oplossen van dit issue: zoeken naar bron/oorzaak o.b.v. analyse van data + vinden van oplossing.
- In deze fase wordt gekeken of de oplossing volgens plan blijkt te werken. Indien de uitkomst helemaal goed is, kan het issue worden gesloten. Indien de oplossing nog verbeterd kan worden, dan gaan we opnieuw naar de planfase.
- Verification by reporter
- Make offer
- Hour estimate / confirmation
- Require client decision
- Verify offer
- Plan resources
- Assign (max 2 hour)
- Max 2 hour triage
- Re-choose hour allowance
- Waiting for test deploy
- Customer test
- Investigate customer response
- Ready for client test
- In Review
- Verify specs
- Waiting for client confirmation
- Ready for delivery
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.
- 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.
- The problem is a duplicate of an existing issue.
- 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.
- Won't Do
- This issue won't be actioned.
- Planning planned
- Planning declined
- Commitment accomplished
- Commitment failed
- Commitment cancelled by client