How to read a JIRA issue record

Owned by Christine Di Bella
Last updated: Mar 17, 2023
2 min read

Key to a JIRA issue record

  1. Type - See the Glossaries for descriptions of the types in use by ArchivesSpace.
  2. Issue Key - a unique identifier for the issue
  3. Summary - a short, usually one-sentence, description of the issue
  4. Description - a fuller description of the issue (not always used if the summary describes the issue in enough detail)
  5. Status -  indicates where a story is in the development workflow.  In the active ANW project, the major status options, in workflow order, are Newly Added > Awaiting More Information > Awaiting Prioritization > Ready for Implementation > Assigned to Developer > Development Started > Ready for Testing > Ready for Inclusion in Release Candidate > Closed - Complete, Closed - Will Not Do, or Closed - Duplicate (You can also view the full Workflow Diagram and Narrative, with all statuses.)
  6. Assignee - the developer tasked with working on the issue
  7. Reporter - the person who first logged the issue into JIRA
  8. Labels - keywords that relate to this issue; one or more labels may be applied. See the Glossaries for descriptions of many of the labels currently in use.
  9. Priority - a relative level of priority to the community or the health of the application. See the Glossaries for definitions.
  10. Comments - Additional information about the user story, such as adjustment to descriptions or specifications, references to related user stories or sources, or explanation of why a user story was not accepted. 
  11. Notifications/Watch/+1 options - buttons to further interact with the issue, including the option of being notified when anything is updated on it.

Not pictured

Attachments - some issues have external documents such as specifications or screenshots that further describe the issue

Dates - indicates when the issue was created and last updated in JIRA.