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
Test
Represents a Test
Test Set
Represents a Test Set
Test Execution
Represents a Test Execution
Pre-Condition
Represents a Pre-Condition
Test Plan
Represents a Test Plan
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.
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.
Request for clarification
Requirement
OAR Review Question
Unplanned Task
Pre-CDR Question
Request for clarification about a document or a phrase in a document.
Improvement
Process Improvement
Review Minor Observation
Spike
SAFe spike is a time limited investigation to get some knowledge
Review Major Observation
Defect
Observation
A reported situation that can become a risk or an issue
SAFe Risk
SAFe risk for ROAMing project
Ticket
The entity to represent an issue
SKATE
This type is for issues or risks managed by SKA-TE
EPM
This type identifies risk and issues managed by EPM
Feature
SAFe program feature
Verification Event
Enabler
Enabler in the SAFe framework is a particular kind of Feature
WBS change request
Dependency
A dependency between SAFe teams that needs to be resolved to deliver a Feature or Enabler on the SAFe program
Risk
For use with the Risk Register add-on
Document
Change Request
Desks
Objective
An objective that is SMART (specific, measurable, achievable, realistic, time-bound).
Xray Requirement
Xray defect
Xray document
Proof Reading Request
Activity
Expected to take roughly one of more months to complete.
Capability
SAFe program capability
CDR Typo
Used to raised a Typo during a review
IGO
Legal Team Task Type
Strategy
Legal Team Task Type
Report
Legal Team Task type
Treaty
Legal Team Task type
OAR Typo
Minor Observation
Review Questions
For making a question on the document and no action is suggested
Typo
Click this button when you want to create an issue for Typos
Goal
Describes an aspirational step towards achieving a vision, expressed in terms of desired outcomes.
Company
Legal Team Task Type
Contract
Legal Team Task type
Employment
Legal Team Task Type
Litigation
Legal Team Task type
Research
Legal Team Task type
Transition
Legal Team Task Type
Talk
Team Risk
Review Typo
Pre-CDR Observation
An observation requiring an action on the reviewed document or a comment.
Chairs
Architectural Decision
Software Architectural Decision
Recommendation
Milestone
Learning Milestone or fixed date Milestone
Implementation Action
Pre-CDR Typo
Report a typo on a reviewed document.
Review Item Discrepancy
Allie's Test for Review Project Work
OAR Observation
PDR Observation
For PDR panel to submit observations.
PDR Question
For PDR panel to submit questions related to documentation (not observations)
PDR typo
For PDR panel to report typos in documents.
For Sub-Task Issues
Risk Mitigation Task
This is a sub-task spawned from a Risk
Implementation Action (sub-task)
An 'Implementation' action for the ECP.
Sub Test Execution
Represents a Sub Test Execution
Sub-task
The sub-task of the issue
Unplanned Sub-task
Unplanned sub-task
ECP-IMP
ECP Implementation Sub tasks

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.

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.
Full Track
Change Request Full Track
Fast Track
Change Request Fast Track
Essential
Essential Requirement.
Non-Essential
Non-Essential Requirement.
Not Assigned
Priority is not assigned yet.
Useful
Created by JIM during import process
Select One
Created by JIM during import process

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 - Project Lead
The Panel has creates a Ticket by writing a question. The issue is now open.
Change Initiated
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.
Resolved and Closed at f2f
The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
To Do
OAR CLOSED
OAR has been closed
Observation Made
Response Submitted
Response Accepted
Response not Accepted
Response Re-Written
Owner & Responder assigned
In Progress
Under Review
Approved
Cancelled
REJECTED
Observation in Preparation
Enables the Reporter to leave JIRA and return before submitting observation
Observation Submitted
Response in Preparation
Typo Owner assigned
Project Lead - Answers the ticket himself
Project Lead (Luca) decides to answer the ticket
Luca's Team Answers The Ticket
Unresolved
The Ticket is answered with narrative and with an expectation to give more during the f2f. Ticket is unresolved
Resolve and Close
Answer the ticket. Resolve and close. These tickets will not be discussed during the f2f
Resolved (1)
Closed
Team Answers The Ticket
The Project Lead decides a Team member answers the ticket and make a recommendation to take it/not to take it to the f2f
Su
Panelist checks the ticket content an submit it.
Open
BACKLOG
All big ideas are welcome here
Selected for development
Reviewed
(Sub)Task review has been completed and feedback is ready for submission
Delivered
Task has been delivered to its final destination. Final decision is still pending.
Document Owner
Ticket is assigned to owner of the Reviewed Document
Reconciliation meeting
Owner decided the issue requires to be taken to the reconciliation meeting
Program Board Meeting
PB meeting to discuss outstanding Pre-CDR Issues
Owner to Resolve
PB decided the Owner needs to resolve the issue.
Assigned for action
PB decided the issue requires resolution through an action.
Resolved at PB Meeting
Action Resolved
Resolved at Rec. Meeting
Delegated
Document owner delegates the ticket
Parked
Issue has been parked and it will be prosecuted in a later stage
OAR DRAFT
Observation created by reviewer, still under revision before being submitted
OAR OPEN
OAR has been refined by reviewer and is ready to be submitted
OAR SUBMITTED
The observation is discussed among author, IET and consortium
OAR RESOLUTION AGREED
Resolution has been agreed but actions are still pending.
OAR RESOLVED
After discussion and/or implementation, no more action is required
OAR WITHDRAWN
DONE
OAR IN PROGRESS
The discussion/resolution is being worked
OAR TRANSFERRED
The observation is transferred to System CDR
Not Assessed
Reported observation has not been assessed by Risk and Issue owners
under assessment
R&I owners are doing the observation assessment
EPM
Observation has been identified as EPM responsibility.
SKATE
Observation has been assessed as SKA-TE responsibility.
transfer for work
Action plan is given to X for implementation
Work Done
OAR CONCLUSION PROPOSED
A conclusion is proposed to close the observation
OAR CONCLUSION AGREED
The proposed conclusion is accepted as the observation resolution
Assessed
Implementing
Feature decomposed into stories. Teams define build and test the solution
Releasing
Feature is integrated and validated according to QA stages up to release
Funnel
All big ideas are welcome here
Analyzing
Benefit hypotesis and acceptance criteria
Program Backlog
Feature approved by product management
READY FOR ACCEPTANCE
Discarded
Own
The risk is owned by the assignee
Accept
The risk is accepted, default assignee is the RTE
mitigated
Risk exists and a mitigation plan is in place
Mitigate
Risk exists and a mitigation plan is in place
OAR ACTION IN PROGRESS
Agreed conclusion is being implemented
OAR ACTION COMPLETE
Agreed conclusion has been implemented
Submitted
TIMS observation has been submitted in the system
Admin Checked
Administrative check has been completed by officer
Triage done
Triage of the ticket is completed
Assessment Complete
Ticket Assessment has been completed.
Investigation started
Start investigation
Mitigation planned
Mitigation for issue has been defined
Monitor mitigation
Keep looking for mitigation execution
Identified
A document title has been identified
Assigned
Document assigned to author for writing
Draft
substantially complete, available for discussion with peers
approval
(ready for review and approval) [Maturity 4]
Completed
(approved and in eB) [Maturity 5]
test
BLOCKING
Analyzed
The impact and probability of the risk have been specified
Treated
The treatment of the risk has been specified
Author Checking
PROOF READING
BLOCKED
Achieved
NOT ACHIEVED
Review Changes
Solution Backlog
CR Analyse
CR Classify
CR Decide
CR Implement
CR Review
CR Closeout
CR Completed
In Review
Committed
Tested
Verified
Accepted
Repair
Fixed
Review and Test
This status is managed internally by JIRA Software
Ready for Deployment
This status is managed internally by JIRA Software
Review
Peer review status
REALISED
decided
ECP
In Assessment
ON HOLD
Change Submitted
Registered
Proposed
Request Approval
ECP Closed
CCB Request
Implement
Cancel
DISPOSITION
Implementation
Scope Assessment
TCR Review
Detail Assessment
CCB Disposition
Reject
Storage
Deployed
Decommission
Record
Update associated documentation
Execute
Complete
Implementation Complete
Once all implementation steps are complete.
Conclusion Proposed
Planned
Recommendation
Recommendation Accepted
Recommendation Rejected
Responded
Scheduled

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.
Resolved
Issue resolved to satisfaction of Reporter
Done
Work has been completed on this issue.
Fixed
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.
Not Done