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
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
- A big user story that needs to be broken down. Created by JIRA Software - do not edit or delete.
- A problem which impairs or prevents the functions of the product.
- A user story. Created by JIRA Software - do not edit or delete.
- New Feature
- A new feature of the product, which has yet to be developed.
- A task that needs to be done.
- An improvement or enhancement to an existing feature or task.
- Request Review of a Synapse data object by the Access and Compliance Team
- Access Request
- Request to the Synapse Access and Compliance team for access to certain Synapse Data.
- A user interface design task delivered as non-functional wireframe
- Access Restriction
- Request to the Synapse Access and Compliance Team to impose an Access Restriction on a given data object.
- A dataset that needs curation
For Sub-Task Issues
- Technical task
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.
- Blocks development and/or testing work, production could not run.
- Crashes, loss of data, severe memory leak.
- Major loss of function.
- Minor loss of function, or other problem where easy workaround is present.
- Cosmetic problem like misspelt words or misaligned text.
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.
- 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.
- This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
- A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
- The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
- 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.
- Dataset identified as a target of interest
- Ready for Curation
- Dataset files received by curation team
- Curated dataset ready to distribute
- In Acquisiton
- Actively working to acquire the data from the contributor
- Curated Dataset Hosted
- Curated dataset available on sage website
- Ready for Review
- Dataset is ready for review
- Curation In Progress
- Actively working on curation process
- Ready to Host
- Ready for hosting to the public
- Waiting for Review
- Engineering works is complete, but not yet checked into dev
- In Review
- To Do
- IN DEPLOYMENT
- Code has been reviewed and merged, and is waiting to be deployed to production.
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.
- 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.
- The problem is a duplicate of an existing issue.
- 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.
- Won't Do
- This issue won't be actioned.