...
- Issue Key - a unique identifier for the issue
- Summary - a one-sentence description of the issue
- Type - See the Glossaries for descriptions of the types in use by ArchivesSpace.
- Affects Version/s - not currently used by ArchivesSpace, but may be in the futureStatus -identifies the version to which a feature request or bug report pertains.
- Status - indicates where a story is in the development workflow. Options are from beginning to end: Icebox > Started > Finished > Delivered > Rejected (user story returns to beginning of process) | Accepted.
- Resolution - indicates whether or not the issue has been addressed - typical values are Unresolved or ResolvedFixed
- Fix Version/s - not currently used by ArchivesSpace, but may be in the future identifies the version in which the a bug was fixed or a feature implemented.
- 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.
- External Issue ID - the unique identifier from Pivotal Tracker, the system used prior to JIRA and from which many of the issues were imported. This only appears on user stories migrated from Pivotal Tracker.
- Description - a fuller description of the issue (not always used if the summary describes the issue in enough detail)
- Attachments - some issues have external documents such as specifications or screenshots that further describe the issue
- Activity - a log of any changes to the issue as well as a place to participate in discussion of the issue
- Assignee - the developer tasked with working on the issue
- Reporter - the person who first logged the issue into JIRA, usually often an ArchivesSpace Program Team member or but sometimes a member of one of the Advisory Councils
- Votes - The number of votes the issue has received. If you are your institution's member representative, then, when you are logged in, you will also be able to vote on an issue, or see whether you've voted for an issue.
- Watchers - The number of people following the issue and who receive receiving notification when it has been updated. If you are your institution's member representative, when you are logged in, you will also be able to watch an issue, or see whether you're watching an issue.
- Dates - indicates when the issue was created and last updated in JIRA
- 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.