How does Issue Templates for Cloud differ from Server version?

 

We developed Issue Templates for the Cloud and Server versions of JIRA. It allows reporters to create the issues on the basis of templates. That’s how it minimizes the amount of work needed for creating issues that are repetitive in nature.

Why install Issue Templates for Cloud?

Here are some good reasons:

  • A boost in productivity – cutting down the number of repetitive tasks allows teams to save plenty of time and focus on those that really matter;
  • Issue creation is faster – instead of losing time on creating new repetitive issues, your team will start completing them sooner;
  • Consistency across issues – that benefit is especially important in situations where consistency is critical, for instance, in the Service Desk, where you need to provide accurate answers every single time;
  • Error reduction – thanks to templates, teams can create many similar issues without making any mistakes;
  • Flexibility in issue creation – your team will be able to tailor templates with maximum flexibility to create complex issues out of the available templates.

The plugin comes in handy in situations such as employee onboarding, executing marketing campaigns, delivering canned responses for the Service Desk, or other processes that require the repetitive creation of similar issues.

So how does Issue Templates for Cloud differ from the Server version of the plugin?

First, there’s a difference in platforms that are involved.

It shouldn’t come as a surprise that the Server version of the plugin offers many more functionalities to users. That’s because the Server version of JIRA provides developers with much more control over different functionalities, allowing them to significantly customize JIRA processes.

JIRA Cloud is still relatively new and developers who use it are restricted by the platform’s API and its limitations.

Here are four other areas with significant differences between the Cloud and Server version of the plugin.

Information access

The most important difference between Issue Templates for Cloud and Server concerns drawing information into the issues you’re creating.

Variables

The Server version of the plugin includes both static and dynamic variables.

Issue Templates for Cloud contains only static variables at the moment, but we are already working on introducing dynamic variables.

To work with variables on Issue Templates for Cloud, it’s smart to first differentiate between two types of static variables:

  • Predesigned variables – these variables are already included on the platform for use;
  • Custom variables – variables that you define by connecting a value to a key.

Post-functions

Issue Templates for Server allows users to copy values depending on the workflow transition. For example, if the issue status is changed from To Do to Done, a particular value can be copied into an issue field.

Unfortunately, users of Issue Templates for Cloud can’t use that option yet.

Third-party plugin support

Issue Templates for Server can accommodate information coming from third-party plugins installed in the same JIRA instance by adding it to specific issue fields. At the moment, Issue Templates for Server can support plugins such as Insight – Asset Management for JIRA and Checklist for JIRA.

We’re currently working on integrating nFeed as well. Have a look here for a detailed breakdown of all supported fields and custom fields.

That functionality isn’t available in Issue Templates for Cloud yet.

Issue Templates for Server includes a range of other, more advanced options (for example, Copy Epic or Security) that are not part of JIRA Cloud and couldn’t be included in the Cloud version of the plugin.

Why choose Issue Templates for Cloud?

The Cloud version of the plugin is a great pick if you’re just starting your journey with JIRA and you don’t want to risk investing in your own server (and a fully customized JIRA instance) just yet.

If you’re an advanced JIRA user, the Server version of Issue Templates might be a better pick. The Cloud version of the plugin requires the same level of expertise as Issue Templates for Server.

But if you’ve got your server in place, it’s smart to invest in a product that allows you to make the most of of your JIRA instance by gaining more control over issue creation and management.

Interested to see how Issue Templates for Cloud works in practice? Head over here to order a free 30-day trial of the plugin and see how it helps your team to create new issues quicker than ever.

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.