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
-
Template
- Issue Type for Templates
-
Bug
- A problem which impairs or prevents the functions of the product.
-
Task
- A task that needs to be done.
-
Umbrella
-
- For use with Roadmap
-
Feature
-
- New feature requests
-
Story
- Created by Jira Software - do not edit or delete. Issue type for a user story.
-
Improvement
- Improve existing functionality
-
- For use by the Reporting SIG with the LDPQURY JIRA project.
-
- For use by the Reporting SIG with the LDPQURY JIRA project.
-
Tech Debt
-
Documentation
-
Epic
- A big user story that needs to be broken down. Created by Jira Software - do not edit or delete.
For Sub-Task Issues
-
-
-
-
-
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.
-
P1
- highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
-
P2
- normal priority level, must be included in the current development cycle
-
P3
- low priority level, item will be considered for inclusion in the next dev cycle
-
P4
- lowest priority level, nice-to have things that require future discussion and design
-
P5
- P5
-
TBD
- To be determined
-
Highest
- This problem will block progress.
-
High
- Serious problem that could block progress.
-
Medium
- Has the potential to affect progress.
-
Low
- Minor problem or easily worked around.
-
Lowest
- Trivial problem with little or no impact on progress.
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.
- Resolved
- A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
- Closed
- The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
- Building
- 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.
- Draft
- (Migrated on 4 Feb 2024 13:41 UTC)
- Completed
- (Migrated on 4 Feb 2024 13:41 UTC)
- In Review
- (Migrated on 4 Feb 2024 13:41 UTC)
- Blocked
- The issue cannot be worked on because it is blocked by other issues. (Migrated on 4 Feb 2024 13:41 UTC)
- In Code Review
- (Migrated on 4 Feb 2024 13:41 UTC)
- Dropped
- (Migrated on 4 Feb 2024 13:41 UTC)
- In SIG Review
- This issue is under review by a Special Interest Group (Migrated on 4 Feb 2024 13:41 UTC)
- In Refinement
- Issue is better defined and ready for the development team to review and to estimate issue. Not ready for development to begin implementation. Issue may need to be further refined. The issue is currently being worked on by team (PO and/or dev). (Migrated on 4 Feb 2024 13:41 UTC)
- In PC Review
- This issue is being reviewed by the Product Council. (Migrated on 4 Feb 2024 13:41 UTC)
- On Hold in SIG
- The special interest group has reviewed this item and has decided not to act on it at this time. (Migrated on 4 Feb 2024 13:41 UTC)
- Analysis Complete
- (Migrated on 4 Feb 2024 13:41 UTC)
- For Release
- The issue has passed QA and user acceptance (by testing or demo). It can be packaged for release to CI. (Migrated on 4 Feb 2024 13:41 UTC)
- In QA
- Passed all developer testing, deployed to testing environment and ready for QA by Product Owner, as well as performance testing. (Migrated on 4 Feb 2024 13:41 UTC)
- Deployed
- Code and related assets are deployed to Folio CI. Release notes and documentation may be pending. (Migrated on 4 Feb 2024 13:41 UTC)
- Awaiting release
- Use this status when Dev team has finished work, issue has been tested on hosted ref environments, and is ready for bugfix/hotfix release. NOTE: Only used for BugFest BugFix and HotFix release workflows. (Migrated on 4 Feb 2024 13:43 UTC)
- Awaiting deployment
- Use this status for released modules that need to be deployed to BugFest. NOTE: Only used for BugFest BugFix and HotFix release workflows. (Migrated on 4 Feb 2024 13:43 UTC)
- In bugfix review
- Use this status for fixes that have been added to BugFest as BugFixes or HotFixes and need final testing and review. (Migrated on 4 Feb 2024 13:43 UTC)
- Prep Deployment
- (Migrated on 4 Feb 2024 13:43 UTC)
- To Do
- (Migrated on 4 Feb 2024 13:51 UTC)
- In Automated Testing
- Reporting SIG will be doing automated testing before manual QA. (Migrated on 4 Feb 2024 13:51 UTC)
- Backlog
- (Migrated on 4 Feb 2024 13:58 UTC)
- Selected for Development
- (Migrated on 4 Feb 2024 13:58 UTC)
- Approved
- (Migrated on 4 Feb 2024 14:24 UTC)
- Cancelled
- (Migrated on 4 Feb 2024 14:24 UTC)
- Rejected
- (Migrated on 4 Feb 2024 14:24 UTC)
- Under Evaluation
- (Migrated on 4 Feb 2024 14:24 UTC)
- Under TC Review
- (Migrated on 4 Feb 2024 14:24 UTC)
- Submitted
- (Migrated on 4 Feb 2024 14:24 UTC)
- Done
- (Migrated on 4 Feb 2024 14:37 UTC)
- In Development
- This status is managed internally by JIRA Software (Migrated on 4 Feb 2024 15:07 UTC)
- Published
- (Migrated on 4 Feb 2024 15:07 UTC)
- Archived
- (Migrated on 4 Feb 2024 15:07 UTC)
- Under Review
- (Migrated on 4 Feb 2024 15:07 UTC)
- Active
- (Migrated on 4 Feb 2024 15:57 UTC)
- Shut down
- (Migrated on 4 Feb 2024 15:57 UTC)
- To Do
- In Progress
- Done
- To Do
- In Progress
- Done
- Provisionally Accepted
- Deferred
- To Do
- In Progress
- Done
- To Do
- In Progress
- Done
- Done
- Discovery
- Parking lot
- Ready for delivery
- Delivery
- Impact
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.
- Won't Do
- This issue won't be actioned.
- Duplicate
- The problem is a duplicate of an existing issue.
- 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.
- Done
- Work has been completed on this issue.