To make the Template custom field visible on a screen (for example the Jira Create issue screen):
Template is added to the screen.
To add screen to the workflow:
Screen is added to the workflow.
Read more about workflows in the Atlassian documentation.
By default, all subtasks from your template will be generated together with the new issue. Switch off the toggle in the context tab if you’d like to stop them from being created (they will not be deleted - only disabled). See the Context chapter for more details.
To transfer the Template Repository project to the target instance along with the configuration, use the following database tables:
| Table | Description |
|---|---|
| AO_33A75D_FAST_ISSUE | [Issue Templates] - Most Popular gadget configuration |
| AO_33A75D_ISSUETEMPLATES_C | General configuration (agile, use as a template, apply template, custom link, variables, colors) |
| AO_33A75D_IT_CFFIELD | Set of fields configuration |
| AO_33A75D_IT_CONTEXT | Availability configuration: CONTEXT_PROJECT_ID = “1” CONTEXT_ISSUETYPE_ID = “2” CONTEXT_LANGUAGE_ID = “3” CONTEXT_PROFILE = “4” CONTEXT_GROUP_ID = “15” CONTEXT_SCREEN_ID = “17” CONTEXT_REQUEST_TYPE_ID = “18” CONTEXT_USERS_ID = “25” CONTEXT_PROJECT_CATEGORY_ID = “26” |
| AO_33A75D_IT_CREATED | List of issues created from template |
| AO_33A75D_IT_DEFAULT | Default templates configuration |
| AO_33A75D_IT_DETAIL | Configuration of particular templates (template name, category, description, enabled/disabled, issue key, customer portal (enabled/disabled; request types), set of fields (autocomplete, copy), template ID, comment) |
| AO_33A75D_IT_EVENTS | List of events (issues created from template, Events Log) |
| AO_33A75D_IT_PROFILE | Set of fields configuration (last update date/name, username of person who created/updated set of fields, set of fields name) |
| AO_33A75D_IT_SUBTASK | Subtasks configuration (Create conditions) |
| AO_33A75D_OWN_VARIABLES | Custom static variables |
| AO_33A75D_TEMPL_COMMENT | List of comments generated for templates |
In Jira Software Data Center 9.14, the Upload app button on the Manage apps page is now turned off by default. To enable it, you’ll need to configure a system property:
-Dupm.plugin.upload.enabled=true
For instructions on setting up system properties, see the documentation. More information about this change can be found here.
To find post functions and add it to workflow:
| Name | Description |
|---|---|
| Deviniti [Issue Templates] Copy Subtasks | Create subtasks from Template Issue |
| Deviniti [Issue Templates] Copy from Epic | Copy issues from template Epic |
| Deviniti [Issue Templates] Create issues | Create new issue from Template |
| Deviniti [Issue Templates] Disable Template | Use this function to disable or enable Template Issue |
Some post functions require additional actions after step 7 (for example Create Issues).
Apply template might be hidden. Make sure you have Hide Apply Template option unchecked.
Apply template is available under More on the Jira issue view.
Read more about the Global configuration.
This might be caused by conflicting contexts chosen in the Availability tab.
Read more about Context.
To find Template ID:
Template ID is visible on the list.
Go to the Details section of the issue. The template name will be displayed in the Template field.
Attachments can be copied only by Copy Values post function.
Make sure you have Attachments in Set of fields for Copy (not for Autocomplete).
Read more about Copy Values here.
To make epic and issues under epic visible you need to grant BROWSE_PROJECT permission in Template Repository.
As a result concrete user/users will be able to see them.
The reason that subtasks were not created simultaneously with the issue (using template) might be a missing record in your database.
It happens when you create Template’s subtasks without opening them. In this case a proper record is not saved in the database.
Record is saved in the database. Template with its subtasks can be used to create issues.
If you can’t find the answer you need in our documentation, raise a support request.
There are two solutions:
This might happen when you upgrade your Jira version. If you install Jira 10+ the problem doesn’t occur. This is caused by Jira changing its Base URL. To fix it, change the URL (Administration > System > General Configuration) back to the one matching the previous version.
Every user is eligible for a 6-month free trial. If you had 1-month trial license, you can generate another one. Go to the marketplace listing of the app and click Try it free.
Our apps are paid via Atlassian, therefore the billing and licensing system is based on Atlassian policy. Add-ons are billed based on the number of users in your host product. If you have 1 000 Jira users, you should buy matching user tier for apps.
Apps are billed based on the number of users in your host product. For Jira Server 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. If you’re running Jira Software for 1 000 users and Jira Service Management for 500 agents on the same instance, you should purchase the 1 000-user tier for apps.
For server apps, purchase and renewal is half-price if you have an academic license for your Atlassian host product. Server apps are always free for community and open-source licenses.
If you can’t find the answer you need in our documentation, raise a support request.