Sidehistorik
...
| Tip |
|---|
The solution below works with the standard Clone function in JIRA, but is more flexible with the Clone Plus Plugin, with is not so expensive. Especially, check out the possibilities in https://bobswift.atlassian.net/wiki/display/JCPP/clone-plus.properties |
Template Issue Types
So, in the second attempt, I have created a lot of objects that works "in parrallel" of the real isssues, in this case ITIL:
| Issue Type | Template Issue Type | |||
|---|---|---|---|---|
| Incident | Incident Template | |||
| Change | Change Template | |||
| Service Request | Service Request Template |
Workflow
Each Template is assigned to a very simple workflow:
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Notifications
And this is sending no notifications at all, and this is pointless, on Post functions, the "Generic Event" is replaced with a new event "No Notifications" I have implemented under "Events" and "Notification Schemes"
Screens
As the template are created in real projects, all fields and field-configurations (and components) are present with the Template are created.
...
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Filters
In general, filters should exclude the "* Template" issuetypes.
Using Templates
I use the templates in 2 ways - cloning them from a JIRA Dashboard and referencing them from Documentation in Confluence:
JIRA Dashboard
Documentation in Confluence
Here in the sample, a JIRA JQL selecting the correct "Incident Templates" are shown on the Incident Management Procedure:
...