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
Story
Created by JIRA Software - do not edit or delete. Issue type for a user story.
Epic
Created by JIRA Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
New API or Message
Question
A question asked by a ACORD Member.
Issue
To Do
Domain Level Issue
Work Request
Work Request via Email
Certification Request
Development Request
Support Request
Idea
For tracking of ideas that need analysis and discussion to flesh out further detail before potentially becoming new Standards Enhancements or projects.
Release
Deployment request
Change Request
Change Request for change management activity
Infra Change Request
Test
This Issue Type is used to create Zephyr Test within Jira.
Pre-Condition
Represents a Pre-Condition
Task
A task that needs to be done.
Bug
A problem which impairs or prevents the functions of the product.
Improvement
An improvement or enhancement to an existing feature or task.
New Feature
A new feature of the product, which has yet to be developed.
Incident
For system outages or incidents. Created by JIRA Service Desk.
Service Request
Created by JIRA Service Desk.
Service Request with Approvals
For requests that require approval. Created by JIRA Service Desk
Change
Created by JIRA Service Desk.
Problem
Track underlying causes of incidents. Created by JIRA Service Desk.
IT Help
For general IT problems and questions. Created by JIRA Service Desk.
For Sub-Task Issues
Sub-task
The sub-task of the issue

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.

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.

New
The issue has been logged and is has not yet been assigned to an ACORD staff member for PRE-ASSESSMENT.
Ready to Onboard
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.
To Do
Done
Under Review
Approved
Cancelled
Rejected
The issue was closed and rejected by ACORD or the Working group due to it replicating another issue, not meeting other requirements for implementation in the standard.
In Review
The issue is being reviewed by the Working Group and a resolution for the issue has not yet been defined. Once an issue completes review and is approved for implementation it will be 'Resolved' and transition to either BACKLOG or ASSIGNED A RELEASE.
Waiting
Pending
Park
Idea
Release Backlog
The issue has a resolution and has been approved for implementation but is waiting to be assigned to a release.
Active Pilot
Assessment
The issue is undergoing assessment by ACORD staff to determine next steps for the issue.
WG Review
The issue is being reviewed by the Working Group and a resolution for the issue has not yet been defined. Once an issue completes review and is approved for implementation it will be 'Resolved' and transition to either BACKLOG or ASSIGNED A RELEASE.
Review Backlog
The issue has not yet been resolved and is parked for later review. The Issue must first be put back into IN-REVIEW and resolved before being assigned a release. The issue can either transition back to IN-REVIEW, CLOSED � REFERRED, CLOSED � WITHDRAWN or CLOSED � REJECTED.
Release Assignment
The issue has been approved for implementation and has been assigned to a release. Implementation of the issue is underway but not yet complete. The issue will transition to being CLOSED � IMPLEMENTED once the standard has been voted on and published.
Referred
The issue was closed and referred to another standards program (and JIRA project).
WIthdrawn
The issue was closed because it was withdrawn by the requestor.
DRAFT Review
Answered
The issue was closed as it was a question that has been answered.
Candidate Review
Voting
Appeals
Published
Implementation
Argued about
Backlog
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
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
Open
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
Waiting for Member
Ready for Implementation
In Implementation Backlog
WG Draft Review
WG Candidate Review
Nominate
Archived
This status is managed internally by JIRA Software
Ordered
Invoiced
Paid
In Dev
In QA
Ready for UAT
In UAT
Ready for PROD
Clarification Required
In PROD
In Implementation
Pending Dependency
In Code Review
Ready for QA
Waiting for Client
Invoice Raised
Badge Requested
Acceptance
Fail
Pass
Retest
Active
Inactive
Post Release Testing
Blocked / On Hold
Review Complete
New/Pending Dev
Ideation
Decisioning
Designated parties are assessing the gathered info to come to a decision on whether to either cancel the Idea or move it into a queue to be worked.
ACORD Review
Ticket is being assessed by ACORD staff.
With Client
With ASG
Review by BA
ASG - deployment details to be reviewed by BA
Review by QA
ASG - deployment details to be reviewed by QA
Ready for Deployment
ASG - deployment ready for Release Team
Awaiting Sanity Check
ASG - deployment to be sanity checked by BA/TL
Awaiting QA Acceptance
ASG - release acceptance by QA
In Estimation
Estimated
Ready for Dev
On Hold
Reviewed by QA
Preparing
In Progress
Selected for Development

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.

Done
Work has been completed on this issue.
Rejected
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.
Unresolved
A resolution for this issue has not been identified.
Withdrawn
Referred
Answered
Won't Do
This issue won't be actioned.
Declined
This issue was not approved.