Apps documentation
Issue Templates for Jira
Cloud Server/Data Center
Issue Templates for Jira


Server/Data Center

Version 8.x
Version 7.x
Release notes
Articles & Videos
Last updated Apr 16, 2023

Create Structure configuration

Learn the basic post function configuration and get an overview of more advanced options

Add post function

First of all, you’ll need to add the Create Structure post function to your project’s workflow. Here is a short guide with all the basic steps. Different post function modes will be described in the next chapters.


Please remember that using templates requires some initial configuration. Read our use case to see how it works in a real life example.


To add the Create Structure post function to a project’s workflow:

  1. Go to Project settings > Workflows.
  2. Select the workflow and go to Diagram > Edit.
  3. Click on the transition of your choice (in most cases: Create) and go to post functions.
  4. Click Add post function and select Deviniti [Issue Templates] - Create Structure.
  5. Choose the post function parameters and click Add.

    For simple cases we recommend leaving the default attributes unchanged. To learn about more complex use cases, go to Possible configurations.

  6. Publish the changes.
  7. Go to Project settings > Screens and select your project’s Create Issue Screen.
  8. Add the Template field.
  9. Create a new issue.
  10. Select an Issue Type.
  11. Select the Template from the drop-down list.
  12. Fill in other fields and click Create.


The template is applied to the newly created issue. All template’s subtasks and linked issues got created as well.


Make sure that the Create Structure post function is listed under the step Creates issue originally and before Re-index an issue to keep indexes in sync with the database. Otherwise, it might not work.

Jira Issue Templates - Create Structure: Add postfunction
Issue Templates for Jira - Create Structure: Add postfunction

Post function parameters

Parameter Possible values Description Additional information
Operation mode Modify current issue Templates can be applied to issues created in the current project. Users can select a template from the Template custom field on the Create Issue (or any other) screen but they don’t have to. Default setting for most standard cases. The Template custom field needs to be added to the proper screen.
Create new issue Templates create issues in different projects. The target project needs to be defined in the template’s Context configuration.
Template Inherit from current template A template can be selected every time an issue is created or modified. Available templates are listed in a custom field on the Create or Edit issue screen. All settings are inherited from the template currently selected in the Template custom field. Default
Choose a fixed template One particular template is always applied to issues created in the current project. The template can’t be changed or removed. If the template has any subtasks, they will be created every time as well. The list contains Template names that are configured under Template Details > General.
Issue linking Do not create link No link is created between the issue created in the different project and the one created in the current project. Default
Choose a fixed link type Issue created in a different project is linked to the issue created from the same template in the current project. The chosen type of link is applied every time. Both outward and inward links are generated. The list of links matches your global Jira configuration that you can set up under Issues > Issue linking. Learn more
Subtask stage None No additional subtasks are created in the workflow. Default
Choose one of the available stages A subtask with the chosen stage will be created from template during transition. The subtask must be configured beforehand. Learn more
Execute asynchronously False All linked issues are created at once, in the same thread as the current issue. Default
True Linked issues are created one by one in the background. This setting improves Jira performance while creating large structures. Learn more

Possible configurations

By combining the Operation mode with the Template source we get four basic configurations. This short summary should help you choose a setup that works best for you. More details will follow in the next chapters.

  1. Modify current issue and inherit template
  • default mode for most standard cases
  • templates can be applied to newly created issues within the workflow
  • users can change the template in the Template field on the screen
  • all settings are inherited from the template that is currently selected in the Template custom field

  1. Modify current issue with a fixed template
  • perfect for automated workflows where one template is always applied to certain issue types
  • template that is chosen in the postfunction configuration will always be applied to issues created in this workflow
  • the template can’t be changed

  1. Create new issue and inherit template
  • best for creating linked issues in different projects
  • template can be changed in the Template field

  1. Create new issue with a fixed template
  • recommended for automated, repetitive processes
  • most useful for creating linked issues in different projects
  • selected template will always be applied when the issue passes the transition
  • users have no control over the issue creation and can neither change nor remove the template

The issues created from the structure can have any issue type available in the target project. There are two ways to define that:

  1. Choose the issue type while creating each template in the structure.


  1. Specify the issue type under Template details > Context.

Remember to add the chosen issue type to the Template Repository (TEMP) project and to the target project.

Next steps

Need help?

If you can’t find the answer you need in our documentation, raise a support request.