The Create Issue screen will be displayed.
JIRA tickets are submitted and reviewed by many different sources, including developers and customers. Writing effective tickets helps us better manage our backlog, aids in reporting of our product baselines, and enables automation of release notes.
DDF generally uses the following issue types. Choose the Issue type that best suits the issue.
| Issues | Description |
|---|---|
| A problem which impairs or prevents the functions of the product. |
| A significant body of work that encompasses many user stories. |
| A new feature of the product. |
| A unit of work adding capability to the product. |
| A task that needs to be performed that does not impact the software baseline. |
| An enhancement to an existing feature. |
| A task involving software documentation. |
| A task that results from poor design choices or incomplete work. |
| Used for design, investigation, and prototyping to determine feasibility of design strategies. |
Issue type descriptions are also found at https://codice.atlassian.net/secure/ShowConstantsHelp.jspa?decorator=popup#IssueTypes.
The summary field is a high level description of the WHAT needs to be resolved. Consider your audience, the summary needs to clearly and succinctly detail the feature or issue from the user's perspective.
Templates. If functionality change, use user story template (see below). If bug fix, use bug fix template (see below)
Describes the issue from a behavioral perspective (i.e. no implementation details)
Understandable for most audiences, e.g. customer, users, stakeholders
Content should be professional in nature
As a <type of user>, I need <some goal>, so that <some reason>
<Symptom> due to <Cause> [, forcing user to <workaround>]
Choose a priority based on the IMPACT of the issue, indicating the importance. Pay close attention to this field when creating Bug type issues.
| Priority | Description |
|---|---|
| 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. |
Priority descriptions are also found at https://codice.atlassian.net/secure/ShowConstantsHelp.jspa?decorator=popup#PriorityLevels.
The Fix Version/s field indicates the version in which the issue is resolved. For planning purposes, this field can indicate the version this issue is intended to be resolved by.
The description field is a detailed, narrative description of the issue. General guidelines for the description field:
Technical Debt
Spike
Blocker
Critical
Major
Minor
Trivial