Sidehistorik
I've been working on Templating in JIRA, without spending (a lot) of money on a plugin for the 2000 user JIRA that I manage at work.
The first solution was making a TEMPLATE Project and use Clone Plus for cloning Issues to the real projects, but the main problem is that issues in the TEMPLATE project does not have the specific field and field configuration properties for Custom Fields and Field Configurations for the real project, so tempates can be fully filled to a satisfying level before cloning the template issue to a real issue.
So, in the second attempt, I have created a lot of objects that works "in parrallelparallel" of the real isssues, in this case ITIL processes.
...
| Tip |
|---|
The solution below works with the standard Clone function in JIRA, but is more flexible with the Clone Plus Plugin, with which is not so expensive. Especially, check out the possibilities in https://bobswift.atlassian.net/wiki/display/JCPP/clone-plus.properties |
Topics
Indholdsfortegnelse
Template Issue Types
...
| 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 | ||||
|---|---|---|---|---|
|
The workflow has no real value, as cloning is always possible, so Its only a signal to the user and the status field can be used in filters.
Notifications
And this The workflow and Notifications is sending (virtually) no notifications at all, and as this is pointless, so on Post functions , the "Generic Event" is replaced with a new event "No Notifications" I have implemented under "Events" and "Notification Schemes"
...
| Issue Type | Screen |
|---|---|
| Incident | Incident Screen |
| Incident Template | Incident Template Screen |
| Change | Change Template |
| Change Template | Change Template Screen |
| Service Request | Service Request TemplateScreen |
| Service Request Template | Service Request Template Screen |
...
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
| Advarsel |
|---|
A lesson learned the hard way here: Field not on the screen is not the same as the field being empty or none existing. Thus, cloning an "Inciden"t to an "Incident Template" will copy all fields, but they cant be seen afterwards. |
Filters
In general, filters should exclude the "* Template" issuetypes.
...
Rendering on the "Incident Template" Screen, the Custom Field looks like (See Making a AUG ADG like button):
