MEASURE TWICE CUT ONCE
I was a Jira Admin for a large Fortune 500 client supporting over 2,000 people and the teams all requested an easy way to scale projects in a similar fashion. I quickly went into panic mode as I first learned that there is no easy way to cut out manual work associated with templatizing your projects, schemes, workflows and issues in a scalable way and I brainstormed ways to solve this challenge assuming I must have misread this somewhere. Then my Aha moment, I’ll just create a master issue for template Jira and will scale the template across the business on-demand and as they needed it. Well, there was one tiny problem. There was no easy way to do this.
As I dove into requirements with the teams, it all seemed like a similar effort. I noticed quickly that I was going to be doing all the same types of admin tasks in order to support new project creation, schemes, permissions, workflows and issue types. As I consolidated the use cases together and synthesized a solution that would satisfy the business need, I started to grow frustrated and an easy as pie admin task quickly ballooned into a giant effort of manual repetition of tasks that slowly started to push me to a point of no return. As I sat there contemplating how to maintain my sanity, I couldn’t help but scour the internet for other recipes or workarounds that would solve my problem, but to no avail.
Throughout my research phase, I couldn’t help but fall deeper and deeper into depression as I learned that there was no easy way to templatize Jira issue types, projects, and schemes. Luckily, I stumbled on a solution. I’ll just use Power Scripts™ for Jira in order to create a templatized structure upfront and can just rinse and repeat from my template in order to automate this effort and build a repeatable template structure. My goals were simple:
- Simplify project configuration and make it easier for individual project owners to maintain and launch their projects.
- Make it easy for anyone to set up their Jira projects and fire their Jira user story templates
- Reduce the amount of repetitive configuration work that Jira administrators need to do.
- Achieve standardization across projects and shared configurations.
Once I figured out exactly what I needed to do in order for this to work. I put together my game plan and got started. With this simple formula you can:
- Solve Jira issue description templates
- See Jira template examples
- Find Jira issue description templates
- And More
Below you will find step by step on how to build your easy templates for Jira issues.
SIMPLE AND FAST WAYS TO BUILD EASY TEMPLATES FOR JIRA ISSUES USING POWER SCRIPTS™ FOR JIRA
STEP 1: I visit the empty project, and validate that permissions and schemes are created and specified.
STEP 2: I start by calling the issueToCopy() function in order to create issues from a template issue.
STEP 3: Next we bring in the fields we want to copy overusing the createIssue() function. Here I chose to bring over Summary, Description, Priority, and Type.
STEP 4: Next we bring in the fields we DO NOT want to copy over based on the createIssue() function. These are Reporter, Assignee, Labels.
STEP 5: Next we will create a new issue key for the new template and will specify the variables and actions that allow the new issues to be created and populated to the new template.
To finish this off, we will add in a few final steps to make sure we create the right actions needed to populate the template. We’ll use the variables specified above. Here we loop through the baseFields and grab the values from the template.
We also want to ensure that we copy from the base template Jira, the createIssue() function so that new issues from the template copy over to the new issues.
Finally, we want to loop through the extraFields in order to assign values from the template to the new issues and return the key to the new issues.
STEP 6: Almost done, we will now specify the new key to determine where we will put these new issues and we will create going forward as we duplicate from the template.
STEP 7: Last but not least, we want to grab all work items from the template and connect it all up in the new project. Here, we will get all stories in the Epic to ensure epic to story links are maintained. We also want to create new stories as a part of this Epic. For that reason, we will also create new stories from the template. We will get all subtasks from the template story and create new subtasks from the template. This will ensure they too are tied to the story.
Finally, we will visit the issue search to validate and ensure that all was a success.
OTHER RECOMMENDED TEMPLATE SOLUTIONS SOLVED WITH POWER SCRIPTS™ FOR JIRA
Tagged with: bulk issue templates in jira, issue template automation in jira, jira, jira automated templates, jira automation templates, jira issue templates, power scripts
Categorized in: Automation, Issue Template Automation, Jira Admin, Power Scripts, Templates, Workflows