- Template management
- Create a template
- Template Navigator
- Template details
- Direct links
- Use as a template
- Delete a template
- Using template
- Create Structure
- Apply template
- Comment field support
- Default template
- Global configuration
- Set of Fields (Scope)
- Template Repository Management
- Event log
- JQL Searchers
Use Case - Jira Webinar
See an example of how to use Create Structure in a project
Your team spent a lot of time and effort preparing an event. Why not profit from what you’ve achieved and save it for the next time? You can reuse the entire work schedule using Issue Templates.
Let’s use the Create Structure post function to organize a webinar for developers. We’ll create an epic with stories, sub-tasks and attachments, so we’d better start with some initial configuration.
Fields & Screens
First of all, we need to have proper fields available on our Create Screen.
- Open Template Repository project settings and select Screens.
- Go to TEMP: Templates Field Screen.
- Add new fields. (In our example: Template and Epic Name).
- Drag and drop to rearrange the fields in the desired order.
You may also remove the fields you don’t need to make the initial screen short and tidy.
By default, there are only two issue types in the Template Repository (TEMP): Template and Sub-template. If we want to build a more complex structure, we need to add other issue types manually.
- In Template Repository’s projects settings, select Issue Types.
- Go to Actions > Edit issue types.
- Drag and drop desired issue types* from the table on the right to the one on the left.
- Click Save.
*In our case: Epic and Story.
Set of fields
Next, we need to set up the Set of fields in order to choose which types of fields should be autofilled in our project. We can choose an existing set or add fields manually.
- Open Template Repository project settings.
- Select Set of fields.
- Add new fields. (In our example: Description, Summary, Attachments and Epic Name.)
- Select the field mode with a toggle.
In our example, we’ll use the Overwrite mode, so that those fields in the target issue will be filled in with what’s written in the template. If you’d like those fields to be editable in the target issue, just switch the toggle to turn it off. Read only mode would block editing and make the fields greyed out.
Create New Template
Now the initial configuration is ready and we can create our template.
Let’s build an Epic - the main issue containing our structure. For more complex projects, you’ll be able to link two or more epics together later on.
- Go to Projects > Templates (TEMP) and click Create in the upper bar.
- Fill in the fields you’d like to be autofilled in your future projects and click Create at the bottom of the form.
Now it’s time for Stories - more specific issues that will bind together related sub-tasks.
- Open the newly created Epic and change the Default Template Name to something recognizable to easily find it later.
- Click on the plus icon next to Issues in Epic.
There are three Stories in our example: Presentation, Mailing and Social Media. Let’s create sub-tasks and see how they can be linked to each other.
- Open the newly created Story (in our example: Presentation).
- Go to More > Create sub-task.
Our first sub-task is related to the presentation’s content and must be completed before other colleagues start working on the visual aspects of our webinar: graphics and presentation slides. Let’s see how we can make that relation visible within our project.
- Open the task you’d like to relate to another Template issue.
- Go to More > Link.
- Add new fields. (In our example: Description, Summary, Attachments and Epic Name).
- Select the field mode* with a toggle.
Tip: This function allows us to connect our template to any other issue, as well. If we select relates to from the drop-down list, we’ll be able to choose from all issues we’ve created before:
Implement Create Structure
Now that our template structure is ready, we can use it to create a new project.
- Open your target project (in our case Basic Software Development).
- Go to Projects Settings > Workflows.
- Select the default workflow and click on the edit icon under Actions.
- Click on the first transition (Create) and go to Post Functions.
- Click Add Post Function and select Deviniti (Issue Templates) - Create Structure.
- Remember to Publish the changes.
- Go to Project Settings > Screens and select your projects Default Issue Screen.
- Add the Template field.
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.
We are all set to create our structured issue:
- Select the project you’ve set up before (in our case Basic Software Development).
- Select Issue Type (in our case Epic).
- Select your template from the drop-down list (in our case JIRA Webinar).
- Define the Variables and click Replace All.
- Fill in other fields and click Create.
If you’d like only your main template (for example epic) to be visible on the create issue screen, just disable all subordinate issues (it doesn’t apply to sub-tasks). Read more about Availability here.
We’ve created a structured template that can be reused anytime to quickly set up a complex project:
- Stories are listed under the Epic
- Tasks appear under Stories
- The relation between tasks is visible
- Attachments get copied into proper tasks
- Variables get replaced in the whole structure