You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
This procedure details the minimum requirements for creating a JIRA ticket to ensure the tickets are consistently filled out and contain sufficient information/ references to information for the assignee to do the ticket. Before creating the ticket identify which project the ticket is for. Ensure the ticket does not include multiple projects on JIRA if it does a ticket should be raised for each project and if there is comonality of task the tickets in other projects should be referenced. This should ensure each project has proper audit trails of work done.
Fields that must be Populated
| Field | Content | Notes |
|---|
| Issue Type | Task/Bug/Improvement/New Feature | Options vary depending on the project definition. Choose most appropriate |
| Summary | Text | Brief heading clearly indicating what ticket is about |
| Description | Text | Detailed description explaining what is required/issue etc. Should include links to further documentation or additional test files as required. |
| Component/s | Drop Down | Select any of the listed components that this ticket applies to. Not all projects will have components defined. |
| PID Data | Text | If any PID information is required for the Assignee to do the Ticket it should be put in this field. This prevents the PID info being included in emails and summaries. |
| Priority | DropDown | Select an Appropriate priority |
|
|
|
Fields that could be Populated
| Field | Content | Note |
|---|
| Affected Ver | Version No | On Software related projects where each release has a version number this should indicate which version was being run when the issues was found. This is primarily applicable to Bugs |
| Due date | Date | When required by a deadline this date should be set. Leave blank if unknown and it can be used to schedule the ticket. |
|
|
|
|
|
|
|
|
|