Advanced Scopes in Issue Templates: A Practical Guide

 

We’ve been busy improving our plugin Issue Templates and one of the things we’ve changed is related to template Scopes.

Read on to learn more about the advanced Scope functionality to make the most of your templates in JIRA.

Scopes in Templates – the Basics

What is a Scope?

A Scope is a set of fields or custom fields that can be used by users to define the fields that will in turn be used for functions like Autocomplete, Copy values, or Copy subtasks.

When creating a template, the user needs to add a particular Scope to it. If the field Description was added to the Scope of the template, applying it to the newly created issue will result in adding the preconfigured value to that field.

That’s how Scopes worked before we revamped them.

What has changed?

Now Scopes can contain dynamic values. That essentially means that the user can map any value to any field.

Here’s How Advanced Scopes Work

To see how that feature works, head over to the project that serves as your template repository and go to project settings.

Click on Scopes to access the configuration panel. You’ll see that the section has changed – when revamping it, we focused on  its design and usability. We made user experience our top priority.

Take a closer look at the table and you’ll notice an additional column entitled Alternative source.

How does Alternative source work? If you add the Description field to your Scope, create a new issue and turn on the Alternative source functionality, you can set your new issue in a way that the value of the Description field will be derived not from the Description field of the template, but from a different field in an altogether different issue.

For example, if you set the Alternative source to ‘from parent’, you’ll be able to add Due Date or any other field from the parent issue to a sub-task.

You can add different fields and configure them in a way that allows to later use them as alternative sources for your templates.

For example, try adding the “Due Date” field and click to turn it on. A screen will pop up where you can choose where to get the value from (no alternative source, parent issue, other issue, current date) and define by how many days the date should be shifted.

You’ll get a completely different selection of alternative source options if you pick a different field.

For instance, if you add “Dynamic Select” to your Scope and pick alternative source, you’ll be able to map the value onto your issue from a different Select field.

Why Did We Introduce Advanced Scopes?

We enriched template Scopes only for dates at first. The idea was to allow users to set up the current date for newly created sub-tasks and allow them to move the date freely.

For example, when creating an issue from a template, users can create a set of sub-tasks where the first sub-task has its current date set in 5 days, the second sub-task has its current date set in 7 days, and so on. Here’s an article to help you create sub-tasks from templates.

Before we implemented that option, users could only change the current date for sub-tasks from the level of the post-function. Tackling the problem from the level of the template Scope, users can add a different Scope to every sub-task and define a different Shift value for that sub-task.

That functionality proved useful for users who wanted to develop a process stretched in time, but didn’t want to lose time on creating issues from scratch.

We implemented the same functionality for mapping text values or Select fields.

Key takeaway

If you’re looking for a comprehensive templating tool for JIRA, consider giving Issue Templates a try.

We’re constantly working on the plugin and plan to improve its functionalities to reflect the needs of organizations in the most accurate ways.

Interested to see Issue Templates in action? Head over here for a free 30-day trial and see how templating can boost the performance of your team.

About Krzysztof Skoropada

As a Head of Atlassian Apps, together with a team of 130 experts, I help companies select the correct plugin for Atlassian according to their individual needs. I am proud of the fact that more than 2 million people from companies such as listed below are trusted clients: CISCO, Ferrari, Samsung, KBC Bank, Deloitte, Allianz, Blizzard Entertainment, Lufthansa, Walmart, Spotify, Sony, MetLife and many more.
Comments are closed.