Jira - Local help - SoftwarePlant 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

IT Help: For general IT problems and questions. 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
Test Run: QTM Custom Issue Type
Test Scenario: QTM Custom Issue Type
Feature: SAFe Feature
Bug: A problem which impairs or prevents the functions of the product.
Test: This Issue Type is used to create Zephyr Test within Jira.
New Feature: A new feature of the product, which has yet to be developed.
Task: A task that needs to be done.
Improvement: An improvement or enhancement to an existing feature or task.
Other
Technical
Custom Dev: Used by Sales project
Demo
Consultancy
Partner Training
Sponsorship
License: Used by Sales project
Training Inquiry
Training - Paid
SAFe Capability
Objective
Story: Created by Jira Software - do not edit or delete. Issue type for a user story.
Incident
Internal Bug
Partner call
Support
Premium Support
Direct Sale: License sold directly
SAFe Enabler
Measure
Review: A review submitted in the Atlassian Marketplace
Partner: Used by Customer project
SAFe Epic
Test Case
Asset
Book
Knowledge Base
Reseller
Log
Feedback
UX
Unknown
Docker
Customer: Used by Customer project
Mother Base
Press Release
Event
Text

For Sub-Task Issues

Technical task: Created by JIRA Agile - do not edit or delete. Issue type for a technical task.
Training Session
Meeting
Sub-task: The sub-task of the issue
Person

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.

Turbo
Blocker: Blocks development and/or testing work, production could not run.
Critical: Crashes, loss of data, severe memory leak.
Major: Major loss of function.
Minor: Minor loss of function, or other problem where easy workaround is present.
Trivial: Cosmetic problem like misspelt words or misaligned text.
None
High: Serious problem that could block progress.
Medium: Has the protential to affect progress.
Low: Minor problems or easily worked around.

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: The issue is open and ready for the assignee to start work on it.
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.
Done
In Review
To Do
Postponed
In Backlog
Selected for Development
Rejected
Proposal accepted
Solution Accepted
Invoicing
In QA Review
Waiting for Release
JOB - New
JOB - Preselected
JOB - To invite for an interview
JOB - Invited for an interview
JOB - Interview finished
JOB - To employ
JOB - Employed
JOB - Employed Finished
JOB - Rejected - Noteworthy
JOB - Rejected
JOB - Not Verified
In Analysis
Paid
Lead
Opportunity
Offer
In decision
Accepted
Awaiting customer
Pending
End of trial
End of trial reminder sent
Welcome mail sent
Unprocessed
Inactive
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
Pending 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
Work in progress: This was auto-generated by JIRA Service Desk during workflow import
Closed Manually
In progress - Investigation
Active
Cancelled
Expire soon
Refund
Scheduled: Scheduled training
Invoice and feedback: Invoice and feedback after training
Q to issue: Sales - Quotation to issue
Q sent: SALES - Quotation sent
Await Q Paid: SALES - Awaiting Quotation Paid
Q paid: SALES - Quotation paid
Post Q Inv sent: SALES - Invoice to send
Inv issued: SALES - Invoice issued
Inv sent: SALES - Invoice sent
Await Inv Paid: SALES - Awaiting Invoice paid
Inv paid: SALES - Invoice Paid
Inv to issue: SALES - In to issue
JOB - Homework
JOB - To ask for a homework
JOB - Rejected to answer
Registered
Waiting for customer: This was auto-generated by Jira Service Desk during workflow import
Gathering interest
To Refactor
Archived
Waiting for Merge
In Test Scenario Review: Release Team verifies that test scenarios has been updated or created.
Pending Partner
Waiting
Postmortem
On hold: The status used for the work that was in progress but had to be stopped and waits to be started again.
Q issued: Quotation issued, ready to be sent
Partner order to issue: Issuing order for partner who will perform the service on behalf of SP
Partner order issued
Partner inv to issue: Issuing commission invoice for the partner
Partner inv issued
Scheduled by Partner: Training scheduled between the partner and the client
Awaiting Q acceptance: Quotation sent. Awaiting its acceptance.
Q accepted: We have a formal acceptance of our quotation.
Await initial payment: Waiting for the initial payment to start work
Backlog
Preparation
Completed
Pending Approval
In consulting review
On Marketing's End
TL Assessment
OK - Needs Marketing Check
Needs Correction
Marketing Assessment
OK - Ready To Answer
Edit Details
Agent Action
Flagged
Flagged - To Address
To be Automated
Retrospection
In Repair

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
Duplicate: The problem is a duplicate of an existing issue.
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.
Declined: This issue was not approved.
Known Error: The problem has a documented root cause and a workaround.
Hardware failure
Software failure