Jira - Local help - JIRA

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

General
DATA Act Broker
Data
Data Change: A change to data within an environment.
Config Change: Modified from JIRA Service Desk.
UX: User experience work.
Triage: An operational issue (usually non-production) that needs to be triaged and assessed.
Feature: Feature Level
DEV-Story: sample story template
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.
Question: Have a question about how something works? Use this issue type.
Story: A user story. Created by JIRA Software - do not edit or delete.
Incident: For system outages or incidents. Created by JIRA Service Desk.
Service Request: Created by JIRA Service Desk.
Problem: Track underlying causes of incidents. Created by JIRA Service Desk.
Schema / DAIMS
Platform
Production Change Request: Issue to support approval workflow of change requests that went into effect March 11, 2022
Epic: A big user story that needs to be broken down. Created by JIRA Software - do not edit or delete.

For Sub-Task Issues

Sub-task
Defect Sub-Task
Data Change Sub-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.

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.

Blocked
Done - Discard
To Do Items: The issue is open and ready for the assignee to start work on it.
In Development: 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.
New
Done: The planned work is Done to an acceptable state.
Story candidate: This status is managed internally by JIRA Software
Product Backlog 1: This status is managed internally by JIRA Software
Release Backlog: This status is managed internally by JIRA Software
Backlog
Selected for Development
Candidate stories: This status is managed internally by JIRA Software
Acceptance Testing: This status is managed internally by JIRA Software
De-Scope: Items added to the backlog, but have now been descoped.
Prioritized
Acceptance: This status is managed internally by JIRA Software
Triage
Blocked
PMO Triage
Scheduled
Waiting for Supervisor
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
Awaiting approval: This was auto-generated by JIRA Service Desk during workflow import
Ready to Implement: This was auto-generated by JIRA Service Desk during workflow import
PMO In Progress
PMO Open
PMO Resolved
Archive: Status of archived Issues/Requests.
Invalid: Status of Invalid Issues/Requests.
In Review: This status is managed internally by JIRA Software
Duplicate: Status to capture duplicates
Out of Scope: Captures items once in scope and now out
Ready for Team Assignment: This status is managed internally by JIRA Software
Need to Address: New ticket
Under Review
OBE: This status is managed internally by JIRA Software
Unprioritized
Rejected
Ready for Team
In Analysis: This status is managed internally by Jira Software
Obsolete: This status is managed internally by Jira Software
Approved: This status is managed internally by Jira Software
Dev Testing
Testing
To Do: New work to be done
In Progress
Waiting or Blocked: This status is managed internally by Jira Software
Draft: Edit details about what change is being requested to production
Implementing
Pending
Canceled
Planning
Awaiting CAB approval: Have the change manager present the change to an approval board.
Completed
Work in progress
Escalated
Under investigation
Defining: A state where the work to-be-done is being defined.
Broken Down: Decomposed and ready for work.
Hold/Blocked: Stopping progress on something and putting it on hold.
Ready to Deploy
Adjudicated: Make a formal judgment or decision about a problem or disputed matter. Deciding how to handle it (a proposed change, a workaround, etc.).
Review: This status is managed internally by Jira Software
Ready for Sprint: Some degree of planning or analysis has happened to distinguish this from a plain 'To Do' item. For instance adding Acceptance Criteria.
Demo: Development work completed and the issue's features are ready to demonstrate.
Failed: A holding state for issues that failed some acceptance criteria and need fixes before moving on in the workflow.
7. Mockup
1. Define Scope
2. Wireframes
3. Design Check
5. Copy
4. User Testing
6. Dev/PM Review
PO Review
9. Spec
Deployed: This change was deployed to production
Pending Deploy: Put an implemented change into a holding state, and schedule it for a future deployment.
FDG Dev: This status is managed internally by Jira Software
EDI API Build: This status is managed internally by Jira Software
Fiscal Data: This status is managed internally by Jira Software
Peer Review: Data Lab - Peer Review
QA Testing: Data Lab - Quality Assurance Testing
Release Ready: Data Lab - marked as ready for release
In Production: Data Lab - In Production - indicates story is available on prod
Finish Metadata and EDI Requirements: This status is managed internally by Jira Software
To Do
In Progress
Done
Review
Ready To Do
Demo/ Acceptance
Waiting for CA
In Testing
Waiting for Approval
Costs Approved
Cancelled
Deploy Ready
Design Review: This status is managed internally by Jira Software
Prioritized for Analysis: This status is managed internally by Jira Software
Metadata Business Line Rev: This status is managed internally by Jira Software
Descope: This status is managed internally by Jira Software
Metadata Requested
Requirements Provided to DTI
Business Line Review: This status is managed internally by Jira Software
To Do
In Progress
Done
To Do
In Progress
Done
In Review
In REview
Closed
QA Review: This status is managed internally by Jira Software
De-scoped: This means we have decided not to move forward with this.
Concept Developed
Data In Progress
Design In Progress
Dev Hand off
Published
Denied: The approval board denied moving forward with the proposed work.
Testing in Temp Env: Ready for testing in a temporary side-environment that is not in the path to production.
Acceptance in Temp Env: Ready for review and acceptance by PO in a temporary side-environment that is not in the path to production.
Failed in Temp Env
Demo in Temp Env
Holding in Temp Env
Approval: Waiting for approval manager to approve or deny the work.
Null: This status is managed internally by Jira Software
De-scoped
Backlog Items
Published/Done
In Progress
On Hold
Design in Progress
Dev Hand Off
Backlog
Concept developed
Data in progress
Design in progress
Dev handoff
Published
Data Review: Data reviews this and moves it to design review
To Do & Unassigned
In Progress
Done
Blocked
In Review
Initial FDG Data Work: This status is managed internally by Jira Software
Requirements Provided to EDI
UAT Business Line Review
To Do
In Progress
Done
To Do
In Progress
Done
To Do
In Progress
Done - Keep

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.
Duplicate: The problem is a duplicate of an existing issue.
Declined: This issue was not approved.
Obsolete: This issue is no longer applicable
Won't Do: This issue won't be actioned.
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.
Workaround: The issue was resolved with a workaround rather than solving the root cause.
Decomposed: This issue was broken down into many other issues that replace it fully
Shelved: Work that was viable, and may be in the future, but we do not foresee doing it anytime soon, and so will put it on the shelf. It can be found later if it is reprioritized.