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

Technical Requirement: Requirement that describes a technical approach to satisfy a business requirement. This will need to be implemented via one or more coding stories. (Migrated on 25 Oct 2022 10:13 UTC)
Initiative
Test Case: A test case to be discussed, described, and implemented (Migrated on 25 Oct 2022 13:33 UTC)
Quest: A set of tasks that need to be completed to satisfy a requirement (Migrated on 25 Oct 2022 13:33 UTC)
TestIssueType
Business Requirement: Requirement that captures business needs in the format of a User-Story. It describes what functionality is expected, by whom and why it is relevant. It should be broken-down into Technical Requirements before implementation. (Migrated on 4 Nov 2022 11:01 UTC)
Test
Demand
Task: A small, distinct piece of work.
Product Requirement: Requirement that describes a business use case that needs to be solved via a new feature or software. (Migrated on 25 Oct 2022 10:12 UTC)
Bug: A problem which impairs or prevents the functions of the product. (Migrated on 25 Oct 2022 10:12 UTC)
DataModel: (Migrated on 4 Nov 2022 10:59 UTC)
Story: Stories track functionality or features expressed as user goals.
Requirement (Test): This issue type has been created for test purpose and attach to Jira project "Requirements"
Epic: A big user story that needs to be broken down. Created by Jira Software - do not edit or delete.
Saga: A collection of epics (Migrated on 25 Oct 2022 10:14 UTC)

For Sub-Task Issues

Sub-task
Detailed requirement

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.

Blocker: Blocks progress on the main deliverables
Critical: Needs to be fixed urgently, or is otherwise in the critical path of the project
High: Task to be completed ASAP, unless something more critical comes along
Low: Good task to do when there is nothing else to work on
Descoped: No longer relevant; here for historical purposes only

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.

REQ Backlog: The issue is in the backlog, ready to get its precise description, Definition of Ready (DoR), Definition of Done (DoD)...
In Progress: 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: (Migrated on 25 Oct 2022 10:12 UTC)
In Test: Module is being tested (Migrated on 25 Oct 2022 10:13 UTC)
Draft: Still being written (Migrated on 4 Nov 2022 10:59 UTC)
Compliant: (Migrated on 4 Nov 2022 11:03 UTC)
Not Compliant: (Migrated on 4 Nov 2022 11:03 UTC)
Partially Compliant: (Migrated on 4 Nov 2022 11:03 UTC)
Not Applicable: (Migrated on 4 Nov 2022 11:03 UTC)
Approved: (Migrated on 25 Oct 2022 10:12 UTC)
Cancelled: (Migrated on 25 Oct 2022 10:12 UTC)
Rejected: (Migrated on 25 Oct 2022 10:12 UTC)
Selected for Development: (Migrated on 4 Nov 2022 11:03 UTC)
Backlog: (Migrated on 4 Nov 2022 11:03 UTC)
On hold: (Migrated on 25 Oct 2022 13:33 UTC)
Selected for Dev: Development team has picked up this technical requirement for implementation (Migrated on 25 Oct 2022 10:13 UTC)
Unconfirmed: This requirement was added for the S@H imported prplWrt workflow (Migrated on 25 Oct 2022 10:12 UTC)
Merged In Master: This requirement was added for the S@H imported prplWrt workflow (Migrated on 4 Nov 2022 11:01 UTC)
Released: This requirement was added for the S@H imported prplWrt workflow (Migrated on 4 Nov 2022 11:01 UTC)
Action Required: This requirement was added for the S@H imported prplWrt workflow (Migrated on 4 Nov 2022 11:01 UTC)
Ready for Review: (Migrated on 4 Nov 2022 11:01 UTC)
Accepted: (Migrated on 25 Oct 2022 10:12 UTC)
Waiting for feedback: We need some more information from the community/reporter/... (Migrated on 25 Oct 2022 10:12 UTC)
Selected for Technical Review: Technical team has selected this product requirement for review and conversion into technical requirements (Migrated on 25 Oct 2022 10:12 UTC)
In Review: (Migrated on 4 Nov 2022 11:12 UTC)
To Do
In Progress
Done
Ready for planning: This status is used to declare that the requirement is refined. It means that all the fields are filled up (DoR, DoD, Due Date ...) and it is now ready for planning.
Ready for Dev: The requirement is now planned and is ready for dev.
Ready for integration: The code is now pushed on Gitlab and ready for integration
Integration In Progress: Integration In Progress. This status is unstable since the dev can come back to in progress for tunning purpose.

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.
Won't Do: 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.