Learn the basic post function configuration and get an overview of more advanced options
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:
For simple cases we recommend leaving the default attributes unchanged. To learn about more complex use cases, go to Possible configurations.
The template is applied to the newly created issue. All template’s subtasks and linked issues got created as well.
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 |
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.
The issues created from the structure can have any issue type available in the target project. There are two ways to define that:
OR
Remember to add the chosen issue type to the Template Repository (TEMP) project and to the target project.
If you can’t find the answer you need in our documentation, raise a support request.