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
Task
A task that needs to be done.
Expense Report
Donation Certificate Request
Project Proposal
Rainbow Incubator Project Proposal
WeChat Group Application
Bug
Volunteer Application
Scholarship Application
PR case
Social Media Post
Epic
Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
Annual Party Refund Request
To request the refund of your annual party ticket.
Story
Created by Jira Software - do not edit or delete. Issue type for a user story.
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.
Normal
Nothing special.
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.

Open
The issue is open and ready for the assignee to start work on it.
Pending Review
This request is received and is being scheduled to be reviewed 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.
In Review
Pending Payment
Paid
Cancelled
Rejected
To Do
Done
HR Screened
Approved
Interviewed
Welcomed
Accepted
Offer Declined
In Progress
Collecting Votes
In Trial
Contacting
Negotiating
Contract Confirmed
Payment Confirmed
In Execution
Payment Closed
Collecting Feedback
Received
Pending Approval
Refund Rejected
Refund Paid
The refund has been paid

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
Some actions were taken but the issue was determined rejected.
Won't Do
No action will be taken on this issue.
Duplicate
The problem is a duplicate of an existing issue.
Approved
The request got approved
Quited
The volunteer is not longer with CRN