Jira - Local help - sagebionetworks.jira.com

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.
New Feature: A new feature of the product, which has yet to be developed.
Story: A user story. Created by JIRA Software - do not edit or delete.
Task: A task that needs to be done.
Improvement: An improvement or enhancement to an existing feature or task.
1kD Data Access Request: Request to ACT team for access to 1kD data
[System] Post-incident review: Document and share incident learning.
[System] Incident: For system outages or incidents. Created by Jira Service Management.
[System] Service request: A request that follows ITSM workflows.
[System] Service request with approvals: A request that follows ITSM workflows.
[System] Change: Created by Jira Service Management.
[System] Problem: Track underlying causes of incidents. Created by Jira Service Management.
SRC fixVersion
Tower Support: This is used only for issues created via Halp in #tower-support
PEC Data Upload Request
AD: Add Data to Existing Study
AD: Publication Dataset
AD: Add New Study
PEC Request Publication Dataset
PEC Access Request
Data Upload Support Request: Request support for issues related to data upload
ELITE Data Access Requests
Flag: Request Review of a Synapse data object by the Access and Compliance Team
Access Restriction: Request to the Synapse Access and Compliance Team to impose an Access Restriction on a given data object.
Access Request: Request to the Synapse Access and Compliance team for access to certain Synapse Data.
HTAN Data upload support request
I
Support: For customer support issues. Created by Jira Service Desk.
Submit a request or incident: Submit a request or report a problem.
Ask a question: Have a question? Submit it here.
Emailed request: Request received from your email support channel.
Data Reuse Support Request: Request support for issues related to data reuse
Epic: A big user story that needs to be broken down. Created by JIRA Software - do not edit or delete.
Initiative: High-level development objective that spans Epics, Teams, and projects.

For Sub-Task Issues

Technical task
Sub-Task

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 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.

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 exists on the backlog, but may require triage before work can be done.
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 customer/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.
Waiting for Review: Engineering works is complete, but not yet checked into dev
Done
In Review
To Do
Blocked/Monitoring
IN DEPLOYMENT: Code has been reviewed and merged, and is waiting to be deployed to production.
Blocked: This status is managed internally by Jira Software
QA: This status is managed internally by Jira Software
User Story: This status is managed internally by Jira Software
Backlog
Ready for Team
Draft
Approved
Start
QA Review: This status is managed internally by Jira Software
Ready for Dev Triage
To Do
In Progress
Done
BACKLOG
Won't fix: This status is managed internally by Jira Software
Selected for Development
To Do
In Progress
Done
Won't Do
Closed
Blocked/Monitoring
Needs Review
Declined: This was auto-generated by Jira Service Management during workflow import
Waiting for support: This issue is awaiting triage and assignment before work can proceed.
Waiting for customer: This issue requires some additional information from the reporter/customer before work can proceed.
Pending: This was auto-generated by Jira Service Management during workflow import
Canceled: Work on this issue has been cancelled.
Escalated: This issue has been escalated for feedback from another team.
Work in progress: This was auto-generated by Jira Service Management during workflow import
Under Review
Cancelled
Rejected
Waiting for approval: This was auto-generated by Jira Service Management during workflow import
Review: This was auto-generated by Jira Service Management during workflow import
Implementing: This was auto-generated by Jira Service Management during workflow import
Planning: This was auto-generated by Jira Service Management during workflow import
Authorize: This was auto-generated by Jira Service Management during workflow import
Completed: This was auto-generated by Jira Service Management during workflow import
Failed: This was auto-generated by Jira Service Management during workflow import
Awaiting implementation: This was auto-generated by Jira Service Management during workflow import
Under investigation: This was auto-generated by Jira Service Management during workflow import
Awaiting approval: This was auto-generated by Jira Service Management during workflow import
Published: This was auto-generated by Jira Service Management during workflow import
Discontinued: The issue is no longer relevant to the Epic.
Needs Review
Won't Do
Governance Triage: Governance team member has 2 days to confirm request is complete before sending to PI for approval
PI Review: PI has 1 week to respond with approval or denial and 1 week for discussion
Rejection Discussion
Returned to Requester
PI Rejection
ACT Rejection: Rejected by ACT team
PI Approved
Pending Customer Response: The task is on hold pending further information from the customer
Additional data: This status is managed internally by Jira Software
In curation: This status is managed internally by Jira Software
Released: This status is managed internally by Jira Software
Expected Data: This status is managed internally by Jira Software
To Do
In Progress
Done
Triage
Done
Discovery
Parking lot
Ready for delivery
Delivery
Impact
AMP-AD-2.0 wrap up: This status is managed internally by Jira Software
New
Follow-up
Contract Sent
Negotiation
Closed Won
Closed Lost
Done
Discovery
Parking lot
Ready for delivery
Delivery
Impact
Done
Discovery
Parking lot
Ready for delivery
Delivery
Impact
To Do
In Progress
Done
Review/Validate: This status is managed internally by Jira Software
To Do
In Progress
Done
Done
Discovery
Parking lot
Ready for delivery
Delivery
Impact

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.
Duplicate: The problem is a duplicate of an existing issue.
Incomplete: The problem is not completely described.
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.
Done
Won't Do: This issue won't be actioned.
Declined: This issue was not approved.
Known Error: The problem has a documented root cause and a workaround.
Hardware failure
Software failure
Cancelled: Requestor of the work has cancelled their request.