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

Story: Created by Jira Software - do not edit or delete. Issue type for a user story. (Migrated on 6 Apr 2024 19:33 UTC)
IT Help: An IT problem or question.
Bug: A problem which impairs or prevents the functions of the product. (Migrated on 6 Apr 2024 19:33 UTC)
Service Request: A request that follows ITSM workflows.
Category: An issue which is not actionable, it only exists to create a 'category' inside of the Structure plugin. It should never appear in scrums/backlogs/TODO lists (Migrated on 6 Apr 2024 19:33 UTC)
Service Request with Approvals: A requests that may require approval.
Lead: A contact or project that Magfest might want to follow up on (Migrated on 6 Apr 2024 19:33 UTC)
Task: A task that needs to be done.
Feedback: Feedback from staffers or general public. Might not be actionable, just useful to have stored somewhere (Migrated on 6 Apr 2024 19:33 UTC)
Emailed Task: A task that comes in via email (Migrated on 6 Apr 2024 19:33 UTC)
VT Project: (Migrated on 6 Apr 2024 19:38 UTC)
New Feature: A new feature of the product, which has yet to be developed. (Migrated on 6 Apr 2024 19:39 UTC)
Purchase: Track items that need to be bought. Created by JIRA Service Desk. (Migrated on 6 Apr 2024 19:39 UTC)
Change: For system upgrades or alterations. Created by JIRA Service Desk. (Migrated on 6 Apr 2024 19:39 UTC)
Fault: Track system outages or incidents. Created by JIRA Service Desk. (Migrated on 6 Apr 2024 19:39 UTC)
Access: For new system accounts or passwords. Created by JIRA Service Desk. (Migrated on 6 Apr 2024 19:39 UTC)
Misc request: Issues from the internet (Migrated on 6 Apr 2024 19:39 UTC)
Event Request: Department requests to be fulfilled at-event (Migrated on 6 Apr 2024 19:39 UTC)
justjukka: (Migrated on 6 Apr 2024 19:39 UTC)
btristan: (Migrated on 6 Apr 2024 19:39 UTC)
ignore: (Migrated on 6 Apr 2024 19:39 UTC)
Improvement: An improvement or enhancement in the codebase. (Migrated on 6 Apr 2024 19:39 UTC)
Volunteer: An individual who volunteers with us.
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
Event Record

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.

CRITICAL: Must be completed immediately – halt other work to resolve.
+1: This problem will block progress.
0: Normal priority
-1: Minor problem or easily worked around.
S1: Definition: An S1 service request is an immediate technology need from MAGFest. Examples of valid S1 requests include system down events, disaster recovery events, security events, and support for sensitive Human Resources related actions. Response time - 2 hours Resolution time - 48 hours
S2: Definition: An S2 service request is a high priority technology need from MAGFest. These types of requests are Time Sensitive, but are not emergencies. Examples of valid S2 requests include creation and provisioning of accounts for new employees, managing resource allocation and deployment of systems to support a new event instance of Reggie, and responding to renewals. Response time - 1 business day Resolution time - 5 business days
S3: Definition: An S3 service request is a low priority technology need from MAGFest. These types of requests are not time sensitive, and may be completed at any time. Depending on MAGFest’s priorities and the availability of any credit hours, these requests may be deferred to a later date. Response time - 3 business days Resolution time - 30 business days
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.
Beeg: Important to display during Sprint Planning to communicate with others. Not necessarily a blocker or time-sensitive.

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.
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.
Not started
Planning
In Progress
Ready for review
Approved
Done
Performance
In Review
Waiting for support
Waiting for customer
Escalated
Canceled
Done
To Do
Pending
In progress
Reopened
Waiting for support: This was auto-generated by Jira Service Management during workflow import
Waiting for customer: This was auto-generated by Jira Service Management during workflow import
Pending: This was auto-generated by Jira Service Management during workflow import
Canceled: This was auto-generated by Jira Service Management during workflow import
Escalated: This was auto-generated by Jira Service Management during workflow import
Declined: This was auto-generated by Jira Service Management during workflow import
Waiting for approval: This was auto-generated by Jira Service Management during workflow import
Work in progress: This was auto-generated by Jira Service Management during workflow import
Done: This was auto-generated by Jira Service Management during workflow import
Ready For Work: (Migrated on 6 Apr 2024 19:33 UTC)
Backlog: (Migrated on 6 Apr 2024 19:33 UTC)
Blocked Externally: (Migrated on 6 Apr 2024 19:33 UTC)
Won't Do: A task that won't be worked on and/or finished (Migrated on 6 Apr 2024 19:33 UTC)
In Progress: This issue is being actively worked on at the moment by the assignee.
Ack: (Migrated on 6 Apr 2024 19:34 UTC)
To Do
Deferred: This status is managed internally by JIRA Software (Migrated on 6 Apr 2024 19:35 UTC)
Blocked: This status is managed internally by JIRA Software (Migrated on 6 Apr 2024 19:35 UTC)
Waiting for support (migrated): This was auto-generated by JIRA Service Desk during workflow import (Migrated on 6 Apr 2024 19:36 UTC)
Waiting for customer (migrated): This was auto-generated by JIRA Service Desk during workflow import (Migrated on 6 Apr 2024 19:36 UTC)
Approved: (Migrated on 6 Apr 2024 19:36 UTC)
Rejected: (Migrated on 6 Apr 2024 19:36 UTC)
Under Review: (Migrated on 6 Apr 2024 19:36 UTC)
Cancelled: (Migrated on 6 Apr 2024 19:36 UTC)
In Review: (Migrated on 6 Apr 2024 19:38 UTC)
Unreviewed: (Migrated on 6 Apr 2024 19:38 UTC)
Safe Review: Ready for Safe Committee Review (Migrated on 6 Apr 2024 19:38 UTC)
Ready for Safe to Contact: (Migrated on 6 Apr 2024 19:38 UTC)
Ready to Finalize: (Migrated on 6 Apr 2024 19:38 UTC)
Selected for Development: (Migrated on 6 Apr 2024 19:40 UTC)
Deployed: (Migrated on 6 Apr 2024 19:40 UTC)
Purchased: (Migrated on 6 Apr 2024 19:40 UTC)
Expense Submitted: (Migrated on 6 Apr 2024 19:40 UTC)
AfterEvent: Stuff to do after Super event. (Migrated on 6 Apr 2024 19:47 UTC)
To Do
In Progress
Done
Rejected
Waiting on STOPS
Waiting on MAGit
In Progress
Done
To Do: (Migrated on 6 Apr 2024 19:34 UTC)

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.

Fixed: A fix for this issue is checked into the tree and tested.
Won't Fix: The problem described is an issue which will never be fixed.
Done: Work has been completed on this 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.
Duplicate: The problem is a duplicate of an existing issue.
Declined: This issue was not approved.
Closed: Case has been closed and watchlist has been updated.