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
- IT Help
- For general IT problems and questions. Created by Jira Service Desk.
- Service Request with Approvals
- For requests that require approval. Created by Jira Service Desk
- Task
- A task that needs to be done.
- Bug
- A problem which impairs or prevents the functions of the product.
- Service Request
- Created by Jira Service Desk.
- New Feature
- A new feature of the product, which has yet to be developed.
- 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.
- Observation
- A reported situation that can become a risk or an issue
- 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
- Verification Event
- Failure
- Feature
- A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI).
- WBS change request
- Component Version
- Component/module/library releases
- Risk
- For use with the Risk Register add-on
- CM Tasks
- Tasks to be completed
- Concession
- Change
- Change Request
- Desks
- Culture Goal
- Culture Goal
- Xray Requirement
- Xray defect
- Xray document
- Proof Reading Request
- Activity
- Expected to take roughly one of more months to complete.
- PI Risk
- Program Increment risk for ROAMing
- Problem
- Capability
- SAFe program capability
- CDR Typo
- Used to raised a Typo during a review
- Requirement
- IGO
- Legal Team Task Type
- Strategy
- Legal Team Task Type
- Memo Request
- Report
- Legal Team Task type
- Treaty
- Legal Team Task type
- Issue
- Realised risk
- Purchase Request
- A request to purchase an item.
- Document
- Create, update or review documentation.
- Review
- Minor Observation
- Design Issue
- Design issue that requires resolution.
- Milestone
- Learning Milestone or fixed date Milestone
- Use Case
- All the ways of using a system to achieve a particular goal for a particular user.
- EMC Test
- Enabler
- An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance.
- 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
- ECP
- Engineering change proposal
- Vacancy
- Vacant position
- Improvement
- Improvement opportunity, such as test automation, continuous integration, improved design, deployment automation, improved telemetry etc
- RM-Opportunity
- Chairs
- Architectural Decision
- Software Architectural Decision
- Recommendation
- Product
- Solution
- Solution to a Problem
- Incident
- Objective
- Objectives are a summary of the business and technical goals that a team (or team of teams) intends to achieve in the upcoming Program Increment (PI). An objective needs to be SMART (specific, measurable, achievable, realistic, time-bound).
- Implementation Action
- Realized Risk
- RM-Handling
- Handling action for risks and opportunities.
- RM-Risk
- Risk issue type to be used in the risk management project.
- Flow
- Associated with a Use Case.A sequence of actions an Actor performs that yields an observable result of value to a particular user.
- Sub-system Version
- A version of a sub-system, used in the Release Management and Configuration Management process
- System Version
- System releases - ie MID, LOW SW. Configured releases of SKAMPI
- Dependency
- A dependency between teams that needs to be resolved to deliver an Activity / Feature / Enabler etc
- Candidate
- Submitting a candidate for selection as a key person on a Software Contract.
- Integration Event
- Technical Publication Policy Request
- Pre-CDR Observation
- An observation requiring an action on the reviewed document or a comment.
- Pre-CDR Question
- Request for clarification about a document or a phrase in a document.
- Review Item Discrepancy
- Allie's Test for Review Project Work
- Pre-CDR Typo
- Report a typo on a reviewed document.
- Review Typo
- Typo
- Click this button when you want to create an issue for Typos
- Review Questions
- For making a question on the document and no action is suggested
- OAR Typo
- OAR Review Question
- OAR Observation
- PDR Question
- For PDR panel to submit questions related to documentation (not observations)
- PDR Observation
- For PDR panel to submit observations.
- PDR typo
- For PDR panel to report typos in documents.
- Request for clarification
- Unplanned Task
- Spike
- A time limited investigation to get some knowledge
- Review Minor Observation
- Review Major Observation
- Defect
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
- Culture Action
- Culture Action sub-task of Goal
- Unplanned Sub-task
- Unplanned sub-task
- Sub-task
- The sub-task of the issue
- Value Assessment
- A value assessment for a shared objective.
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.
- Essential
- Essential Requirement.
- Non-Essential
- Non-Essential Requirement.
- Useful
- Created by JIM during import process
- Select One
- Created by JIM during import process
- Must have
- Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
- Should have
- Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
- Could have
- Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
- Won't have (this time)
- Items labelled as "Won't have", have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, "Won't have" items are not planned into the schedule for the next delivery timebox.
- Blocker
- The problem will block progress.
- Minor
- Trivial problem with little or no impact on progress.
- Not Assigned
- Priority is not assigned yet.
- Critical
- Major
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
- Issue created
- 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
- Document Update being reviewed by Stakeholders
- 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 (if applicable)
- 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
- OAR IN PROGRESS
- The discussion/resolution is being worked on
- 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
- Funnel
- All big ideas are welcome here
- Analyzing
- Benefit hypotesis and acceptance criteria
- Program Backlog
- Feature approved by product management
- Implementing
- Feature decomposed into stories. Teams define build and test the solution
- READY FOR ACCEPTANCE
- Releasing
- Feature is integrated and validated according to QA stages up to release
- Done
- 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
- Issue has been identified.
- Assigned
- Issue has been assigned.
- 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
- Action is officially planned.
- Recommendation
- Recommendation Accepted
- Recommendation Rejected
- Responded
- Scheduled
- Formalise Prevention
- Monitor Design
- Monitor Build & Test
- Monitor As-built
- Accept Design
- Accept Evidence
- Design Safety Review
- Delivery Review
- Final Safety Review
- Cancellation Review
- Identify Changes
- This status is managed internally by JIRA Software
- Final Review
- This status is managed internally by JIRA Software
- Change Discarded
- This status is managed internally by JIRA Software
- Testing
- This status is managed internally by JIRA Software
- waiting for feedback
- This status is managed internally by JIRA Software
- Waiting
- This status is managed internally by JIRA Software
- Exploration
- This status is managed internally by JIRA Software
- Awaiting Feedback
- This status is managed internally by JIRA Software
- PARTIALLY ACHIEVED
- Subordinated
- Active Risk/Opportunity
- Deprecated
- Retired
- Realized
- Unplanned
- Failed
- testing and documenting
- This status is managed internally by JIRA Software
- Reviewing
- This status is managed internally by JIRA Software
- Document QA
- Registration, Quality Checking
- Update eB
- Update eB Baseline
- TODO
- NOT APPROVED
- PASS
- FAIL
- Validated
- Review Complete
- MEMO Approved
- MEMO sent
- Ready for Review
- In Allocation
- Approved for Publication
- Published
- Created
- This status is managed internally by Jira Software
- Assessment
- Diagnose
- 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
- This was auto-generated by Jira Service Desk during workflow import
- 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
- 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
- Under investigation
- This was auto-generated by Jira Service Desk during workflow import
- Implemented
- Released
- Documenting
- Verifying
- Ensure Outcomes and Definition of Done are satisfied.
- Validating
- User / reporter validates that the issue is addressed.
- Active Risk
- Tranferred
- Basic Flow Agreed
- Basic Flow Fulfilled
- Alternate Flows Fulfilled
- Merge Request
- This status is managed internally by Jira Software
- Ready to Close
- Request to Cancel
- EW
- SKARR
- Hired
- Candidate Selected
- Candidate Received
- Interview Requested
- Ready for Release
- Rework
- New
- Defect
- Concession
- Failure
- Re-Opened
- Draft Ticket
- Corrective Action
- Investigation
- Implement Solution
- Being Implemented
- Feedback
- Ongoing
- This status is managed internally by Jira Software
- Not Scheduled
- Passed
- DO NOT USE
- DO NOT USE THIS Release
- Ideas
- This status is managed internally by Jira Software
- Chosen for Research
- This status is managed internally by Jira Software
- Internal Review
- Rework Internal Comments
- External Review
- Rework External Comments
- Awaiting input
- This status is managed internally by Jira Software
- Closed without Completion
- ECPs closed without completing the implementation work.
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
- Declined
- This issue was not approved.
- Transferred
- The problem is transferred to another ticket or process