Jira Issue Tracker Overview
- Former user (Deleted)
- Jodi Becher
- Former user (Deleted)
Introduction
Jira is the issue tracker used by the SSDT to schedule and track issues related to project development. Below is a list of Jira projects used by the SSDT for redesign development along with a corresponding description of what issues are tracked in each.
Project | Description |
|---|---|
The main USPS-R backlog from which issues are directly prioritized and assigned to a sprint for development. | |
This project tracks issues requested via user feedback. These issues have not yet been excepted and scheduled for development. | |
This is the issue backlog for the USAS-R project | |
This is a common project with shared core code used by both USPS-R and USAS-R. | |
This project contains shared UI (user interface) code shared by both projects. |
Self-registration
Although all projects allow issues to be viewed by anonymous users, some of the project pages linked to above will not allow access unless you have an account and appropriate access has been granted. It is therefor suggested that all State Software Advisory Committee Members (particularly those participating in the prioritization working group) self register for an account. After self registering, if committee members provide their usernames to @Matt Calmes or @Jodi Becher appropriate access can be established. This includes enhanced access to the projects above and access to the shared issue filters described below.
Issue Priorities
Below is a listing of the issue priorities used by the SSDT in descending order from highest to lowest priority. This priority in addition to the times an issues has been requested / reported are the main things that make up an issues overall priority.
Blocker - this priority indicates this issue is preventing a user from actually completing a necessary business function in production and no work around is present.
Critical - this priority indicates a very severe issue that is impacting production processing, but a work around exists or for some reason the patch is not as time critical as a blocker issue would be.
Major - this priority indicates an issue that if completed would provide a significant level of new functionality or corrects a bug whose impact does not reach the level of critical.
Minor - this priority indicates either a feature that would provide moderate benefit if implemented or could represent a bug that is an annoyance, but does not cause a lack of functionality.
Trivial - this is the lowest priority and is typically reserved for improvements that would be "nice to have", but do not significantly increase the usefulness of the software.
Jira Issue Filters
Below are some useful Jira filters that are tailored toward trimming and sorting the backlogs in a way that may prove useful to the specific needs of the issue prioritization working group. Please note you must be a logged in user to use these filters (see self-registration section above).