Jira - Local help - Cornell University Library

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.
Task: A task that needs to be done.
Improvement: An improvement or enhancement to an existing feature or task.
Feature Description: High-level description of a feature--issue is linked to actual tasks or feature.
New Development: Development work that is not a bug--it requires new code.
Story
Small Project: A small project that doesn't need its own project in JIRA
Planning Task: A planning task
Data Correction: review or correction of data
Action: An action that needs to be performed for the project.
Issue: An issue with the project.
User Story: gh.issue.story.desc
Policy Question: An issue requiring a policy decision to resolve
Documentation: An issue pertaining to missing or incorrect documentation
Feedback: End-user feedback
Service: A Service
Project Management: Linked to Airtable
Internal Process
External Issue: Local version of an external issue
In Review
Epic: gh.issue.epic.desc

For Sub-Task Issues

Sub-task
Technical 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.
Low: low
Medium: medium
TBD: To Be Determined - not yet assessed

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.

Description and access
Acquisition
Activation
Maintenance required
In review
New Search Static Site - datab
In Review
Blocked
Won't do
Sory
TO DO - 2023
Watch
Done - Needs Implementation
Open Tickets with Hosting
New
Preliminary investigation
Awaiting selector decision
Licensing
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 not closed can be reopened.
Deferred: Issue has been deferred pending resource availability or change in circumstances
External Hold: Issue is on hold pending action by an external party
Subtask Hold: Issue is on hold pending completion of subtasks
Pending Deployment: Issue is solved and tested, remains open pending deployment
Archivist Ingest/Conversion/Storage
Archivist Quality Control
Audio Engineer Quality Control
Archivist Project Wrap-Up
Project Stored for Later
Callibrate Equipment
Done
In Review
To Do
Open 2015: Open and prioritized for 2015 work
Ideas: This status is managed internally by JIRA Software
Urgent: This status is managed internally by JIRA Software
Awaiting Confirmation: This status is managed internally by JIRA Software
Stalled: This status is managed internally by JIRA Software
historical-to-archive: This if for items that were moved to historical status to be archived
todo
RE-OPENED
Rejected
Building: Source code has been committed, and JIRA is waiting for the code to be built before moving to the next status.
Needs Info
Needs Review: Usually this means that a Pull Request has been raised from a feature branch to the develop branch, and a code review is required.
Build Broken: The source code committed for this issue has possibly broken the build.
Delivered: The feature has been staged for stakeholder review.
Verified: The bug can be reproduced, and can be fixed.
To Do
In Progress: This issue is being actively worked on at the moment by the assignee.
Done
To Do
In Progress
Done
To Do
In Progress
Done
In Development
To Do
In Progress
Done
To Do
In Progress
Done
Ongoing
Waiting on others: This status is managed internally by Jira Software
ON HOLD - COVID
To Do
In Progress
Done
Ongoing Maintenance: This status is managed internally by Jira Software
Evolution and Renewal: This status is managed internally by Jira Software
Backlog
To Do
In Progress
Done
Ongoing Service: This status is managed internally by Jira Software
To Do
In Progress
Done
Wishlist
Stalled
Upcoming
To Do
In Progress
Done
Blocked
Priorities
Cornell top 20
Done
Follow up Need
Open
wont do
Re-Opened
Needs Review
Duplicate
Done - Needs Confirmed
Story
To Do
In Progress
Done
To Do
In Progress
Done
To Do
In Progress
Done
To Do
In Progress
Done
Done - Public Display
Cornell Top 20
Priority
Follow Up
Wont Do
Done - Needs Review
Done - Needs Implementation
Duplicate
Backlog
Selected for Development
Ticket With Hosting
To Do
In Progress
Done
Watching
Reviewed
To Do
In Progress
Done
To Do
In Progress
Done
To Do
In Progress
Done
Open
In Progress
Done
Cancelled
Rejected
In Review
To Do
To Do
Done

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.

Complete: The work for this task is complete and tested.
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.
Table: Postpone resolution pending resolution of more pressing matters
Referred to Development: An VIVO ontology or feedback issue that has been linked to an issue in the VIVONIH space
Reviewed for Pending Action: An issue that has been reviewed for clarity and assignment but not worked on yet
Done
Won't Do: This issue won't be actioned.