I've been working on Templating in JIRA, without speding 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 the use of Clone++ 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 the real project, so tempates can be fully filled before cloning.
Template Issue Types
So, in the second attempt, I have created a lot of objects that works "in parrallel" of the real isssues, in the 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:
Notifications
And this is sending no notifications at all, and this is pointless, on Post functions, the "Generic Event" is replace with a new event "No Notification"
Screens
As the template are created in real projects, all fields and field-configurations (and components) are present with the Template are created.
But, in the template we dont want some specific fields present, that are not relevant until cloning the Template to a real issue - typical Date and Person-related fields, so each Template has its own Screen Scheme and Sceen:
| Issue Type | Screen |
|---|---|
| Incident | Incident Screen |
| Incident Template | Incident Template Screen |
| Change | Change Template |
| Change Template | Change Template Screen |
| Service Request | Service Request Template |
| Service Request Template | Service Request Template Screen |
A sample for the Incident Screens:
Filters
In general, filters should exclude the "* Template" issuetypes.