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
- UI Requirement
- For requirements regarding UI and UX. Created by RTM.
- Support Incident
- An unplanned interruption or reduction in quality of an operational IT service
- Service Request
- A request from a user for something to be provided â?? for example, a request for information or advice; to make an admin change, e.g. reset password.
- Requirement
- Detail-oriented statement of a required system feature, typically more granular than a Story
- Feedback/Report
- Feedback and/or report of user experience that needs review before re-classification as one or more issues
- Experiment
- Defect
- A defect is a deviation from the requirements. Created by RTM.
- Test Execution
- For test executions. Created by RTM.
- Test Case
- For test cases. Created by RTM.
- Test Plan
- For test plans. Created by RTM.
- Business Requirement
- For business objectives and goals. Created by RTM.
- Non-Functional Requirement
- For non-functional requirements. Created by RTM.
- Functional Requirement
- For functional requirements. Created by RTM.
- Analysis
- Pure analysis of a problem
- Support Request
- Risk
- [Project] Ticket that describes a risk
- Mail-In Experiment
- An experiment that is run by beamline stuff with samples that are mailed in
- Standard Access Experiment
- An experiment that is run by Users
- Development Request
- A request for development
- Product Release
- Issue to track progress of a release.
- Minor Task/Bug
- Github Issue
- Issue to capture a linked Github issue
- Restricted Operation
- Machine Downtime
- For Ops Fault Log
- Bug
- A problem which impairs or prevents the functions of the product.
- Epic
- Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
- Story
- Created by Jira Software - do not edit or delete. Issue type for a user story.
- 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.
- Problem
- Track underlying causes of incidents. Created by Jira Service Desk.
- Change
- Created by Jira Service Desk.
- Service Request with Approvals
- For requests that require approval. Created by Jira Service Desk
- Incident
- For system outages or incidents. Created by Jira Service Desk.
- IT Help
- For general IT problems and questions. Created by Jira Service Management.
- Support
- For customer support issues. Created by Jira Service Management.
For Sub-Task Issues
- Sub-task
- The sub-task of the issue
- Story Bug
- A bug in a current story
- Technical task
- A technical task.
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.
- Critical
- Crashes, loss of data, severe memory leak, blocks development and/or testing work.
- Major
- Major loss of functionality.
- Normal
- Loss of a particular option or function.
- Minor
- Minor loss of function, or other problem where easy workaround is present.
- Trivial
- Cosmetic problem like misspelt words or misaligned text.
- Blocker
- The problem will block progress.
- High
- Serious problem that could block progress.
- Medium
- Has the protential to affect progress.
- Low
- Minor problems or easily worked around.
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
- Reopened
- This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
- Wait Triage
- Ticket acknowledged but unclassified. Wait for team to discuss and investigate before assigning for action, or defering to planning and scheduling.
- Wait Scheduling
- Ticket classified as a development issue awaiting prioritisation and scheduling - typically for improvements, new features or user stories.
- Wait Action
- Ticket classified as ready for action - typically review of issues, investigation of defects, or development of critical improvements.
- Active
- This issue is ready to be worked on by the next available person.
- Investigate
- In Progress
- This issue is being worked on now or next by the assignee.
- In Progress: Anlys
- This issue is being worked on now or next by the assignee. Analysing includes investigating, specifying, designing.
- In Progress: Dev
- This issue is being worked on now or next by the assignee. Developing includes coding, wiring, configuring, documenting.
- In Progress: Test
- This issue is being worked on now or next by the assignee. Testing includes reviewing, bug fixing, redoing.
- Review
- Work identified as requiring review before progressing
- Under Review
- A resolution was found and will be inspected by another developer.
- Wait Validate
- This needs to be checked by a tester before closing the ticket
- Testing
- A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
- Wait Deploy
- Mark as development work complete and awaiting deployment
- Resolved
- The resolution is marked complete, not yet accepted.
- Closed
- The resolution has been accepted.
- Deferred
- This issue is acknowledged, but is not yet prioritised for resolution.
- Analysis
- This issue is being worked on now or next by the assignee. Analysing includes investigating, specifying, designing.
- Development
- This issue is being worked on now or next by the assignee. Developing includes coding, wiring, configuring, documenting.
- Validation
- This issue is being worked on now or next by the assignee. Validation includes reviewing, testing, bug fixing.
- Experiment Created
- First POC Made
- Containers Posted
- Received and Stored
- Experiment Running
- Disposal/Return
- Declined
- This was auto-generated by Jira Service Desk during workflow import
- Waiting for support
- This was auto-generated by Jira Service Desk during workflow import
- Waiting for customer
- This was auto-generated by Jira Service Desk during workflow import
- Pending
- A Pending release is planned, but no action has yet been taken.
- Canceled
- This was auto-generated by Jira Service Desk during workflow import
- Escalated
- This was auto-generated by Jira Service Desk during workflow import
- Waiting for approval
- This was auto-generated by Jira Service Desk during workflow import
- Awaiting CAB approval
- This was auto-generated by Jira Service Desk during workflow import
- Planning
- This was auto-generated by Jira Service Desk during workflow import
- Awaiting implementation
- This was auto-generated by Jira Service Desk during workflow import
- Implementing
- This was auto-generated by Jira Service Desk during workflow import
- Peer review / change manager approval
- This was auto-generated by Jira Service Desk during workflow import
- Work in progress
- This was auto-generated by Jira Service Desk during workflow import
- Completed
- This was auto-generated by Jira Service Desk during workflow import
- Under investigation
- This was auto-generated by Jira Service Desk during workflow import
- Done
- This was auto-generated by Jira Service Desk during workflow import
- To Do
- New
- Feedback Needed
- Staging
- Working to deploy to a staging environment.
- Deployment Pending
- All artefacts associated with a deployment are ready and a deployment date is set.
- Ready to Release
- Work has been completed, but not yet released
- Backlog
- Selected for Development
- Ready to Merge
- Code is reviewed and tested, just needs merging into the main codebase
- Ready to Deploy
- Blocked
- This status is managed internally by Jira Software
- In Review
- AMMENDMENT REQUIRED
- AUTHORISED
- POSTPONED
- REMOVED
- Follow up
- This status is managed internally by Jira Software
- Waiting for Shutdown
- This status is managed internally by Jira Software
- On Hold
- Waiting for MP Day
- Created
- Accepted
- In Sprint
- Code Review
- Waiting for third party
- Scheduled
- Work Published
- Proposal
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.
- Deployed
- Work on this issue has been completed and the feature is deployed to production.
- Completed
- The task is now all done
- Workaround
- The problem has been worked around, without making a change to the system.
- 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.
- Non Issue
- The problem described is not an issue, e.g. reporter misunderstood expected behaviour, or made a mistake.
- Duplicate
- The problem is a duplicate of an existing issue.
- Won't Fix
- The problem described is an issue which will never be fixed.
- Incomplete
- The problem is not completely described.
- Done
- GreenHopper Managed Resolution
- Won't Do
- This issue won't be actioned.
- Declined
- This issue was not approved.
- Known Error
- The problem has a documented root cause and a workaround.
- Hardware failure
- Software failure