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
Bug
A problem which impairs or prevents the functions of the product.
Epic
Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
New Feature
A new feature of the product, which has yet to be developed.
Story
Created by Jira Software - do not edit or delete. Issue type for a user story.
Task.
A task that needs to be done.
System Documentation Request
Documents Operations procedures, Nagios requests, and other SISESE/DNOC/Ops-related items
Defect
A problem which impairs or prevents the functions of the product.
Colo Task
Merge Request
Violation Report
Translation
Ticket
Application
Design Issue
Tasks that are enhancements, suggestions, or changes to design
DRT
Deploy Request Ticket
QART
Release
Release QARs
Sim Host Repurpose Request
Meta Issue
Describes a general category of problems rather than a specific problem
Ad Hoc Dataset
Custom Universe
Dashboard Metric
Formatted Report
New Feature Request
Video Request
QAE
Viewer 2 - External QAR Issue type
For Sub-Task Issues
Sub-task
The sub-task of the issue
Task
A task required to complete the story.
QAR
Beta
TPV Deploy Request
Deploy Request Tracker for Third Party Viewers
Story Defect

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.

Showstopper
An issue that could (or did) cause disastrous consequences. For example critical loss of data, critical loss of system availability, critical loss of security, critical loss of safety. Such as the inability for many Residents to login. IMPORTANT: Abusing this setting will cause revocation of Bug Tracker access. If in doubt, mark "Severe" instead.
Severe
An issue that could (or did) cause very serious consequences. For example a function is severely broken, cannot be used and there is no workaround.
Major
An issue that could (or did) cause significant consequences, but there is a workaround. For example: A function is badly broken but workaround exists.
Minor
An issue that could (or did) cause small or negligible consequences. Easy to recover or workaround. For example: misleading error messages, displaying output in a font or format other than what the resident desired.
Trivial
An issue that can cause no negative consequences. Such defects normally produce no erroneous outputs. For example: simple typos in documentation, bad layout or mis-spelling on screen.
Unset
An issue whose priority has not yet been determined

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
Fixed = The fixed is in production. Won't Finish = This issue should not or will not be fixed. Duplicate = Another issue has the same subject.
Fix Pending
When the imported issue has passed QA internally, then the public issue will change to Fix Pending. The bug is fixed in a version of the code that should soon be publicly available.
Ready for Translation
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Translation In Progress
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Translated
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
In QA
Passed QA
Translation Final
Published
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
On Hold
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Editing In Progress
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Edited
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Testing
QA in progress
Verified
Passed QA but not yet integrated
Verified: Fixed
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Verified: Fix Needed
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Republished
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Ready for Testing
Issue is ready to be tested by LL QA
Reviewing
Reviewing issue before considering it "Development Complete"
Deferred
The problem/idea is being evaluated but will not be worked on at the moment.
Passed Testing
Issue has passed testing
Approved
Design Issue fits within the current roadmap, approve it
Rejected
Design issue does not within the current roadmap, reject it
Requested
A QAE has been Requested for a Build.
Failed QA
Closed-BP
Closed-BI
Awaiting Review
Initial state when an issue/ticket is created or when it is reopened from a resolved or closed state. All issues in this state will be reviewed and triaged.
Acknowledged
After upgrade (on Sept 7): When an issue has been imported to an internal Linden Lab project, it will be marked as Acknowledged. We're installing a custom tool to enable syncing between internal and external projects (ie VWR, SVC, WEB). Prior to upgrade: Acknowledge is all issues that were In Progress.
Released
When the imported issue has been released (when it's marked as Closed), then the public issue will be marked as Released and the Resolution = Fixed.
Needs More Info
The issue lacks actionable information. Add the info or it CAN'T be investigated.
Cannot Reproduce
Following the stated steps does NOT show the problem. Please provide a solid description of how to reproduce the problem, otherwise it's like finding Bigfoot. Issues that can't be reproduced will eventually be closed.
Contact Support
The issue does NOT belong in the Issue Tracker. Please contact http://secondlife.com/support
Expected Behavior
This is NOT a bug and functions by design.
Misfiled
This issue doesn't belong in the Issue Tracker.
Deploy Requested
Deploy Failed
Build Requested
Build Failed
Prod Deploy Requested
Prod Deploy Completed
Prod Deploy Failed
Prod Deploy Rolled Back
Integration Test
Integrated and ready for Testing
Preparing RC
Pending RC
In RC
Needs Fix
Pending Release
Delisted
Notified
Violation
Compliant
Been Triaged
Reviewed
Returned
Ineligible
Listed
In Beta
Failed
Fubar
Req SQL Review
SQL Rev Pass
SQL Rev Fail
Req Dply Staging
Staging Deployed
Stage Dply Fail
Req QA
Urgent Dply Req
Release Review
In Review
Product Review
pending approval from Product for integration
Closed - Cannot Reproduce
Closed - Expected Behavior
Closed - Won't Finish
Information Provided
Accepted
ready for qa
This status is managed internally by JIRA Software
Ready for Deployment
This status is managed internally by JIRA Software
Won't Finish
This status is managed internally by JIRA Software
Merging
Blocked
Planning
Development
Pending Beta
Deployed to Test
deployed in some test environment
In Production
Deployed to production, not yet verified there
Integrated
PreQA

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 available in a public release
Duplicate
The problem is a duplicate of an existing issue.
Won't Finish
The problem described is an issue which likely will never be fixed.
Not Applicable
Ticket is not applicable because it is filed in the wrong system, is a support issue, etc.
Incomplete
Ticket is incomplete because it needs more information, cannot be reproduced, etc.
Unactionable
Problem described in the ticket is not in a form that action can be taken (i.e. it's too broad)
Released
The ticket is now in production.
Expected Behavior
Cannot Reproduce
Triaged
Contact Support
Re-opened
Accepted
Problem Found
used in QART issues to indicate not-a-pass