Create advanced structures, e.g. several linked Epics with Stories and Sub-tasks in one click!

If your template contains links to other templates, the app will create issues from those linked templates (remember to add "Linked Issues" field to the scope of a template).

Now links to templates are updated to direct to newly created issues.

Also, fixed problem with additional \ added after replacing dynamic variables.

The following improvements have been made:

* Compatibility with Jira 8.4 has been added.

* Support for Dynamic Variables under Epic/Story structure.

* JQL Criteria for creating Stories under Epic.

* Changing the order how the users and groups from Availability Settings are interpreted.

The following bugs have been fixed:

* Issue Template incompatibility with Structure.

* Custom Field "Checklist" didn't work with the function "Apply Template".

* Multi-line text custom fields using wiki renderer didn't work correctly.

* Problems with applying custom field Customer Request Type.

* Unable to clone the values in "Scope" and "Stages" when cloning a sub-tasks template.

The following improvements have been made:* Compatibility with Jira 8.4 has been added.* Support for Dynamic Variables under Epic/Story structure.* JQL Criteria for creating Stories under Epic. * Changing the order how the users and groups from Availability Settings are interpreted.The following bugs have been fixed:* Issue Template incompatibility with Structure.* Custom Field "Checklist" didn't work with the function "Apply Template".* Multi-line text custom fields using wiki renderer didn't work correctly.* Problems with applying custom field Customer Request Type.* Unable to clone the values in "Scope" and "Stages" when cloning a sub-tasks template.

The following improvements have been made:

* Compatibility with Jira 8.4 has been added.

* Support for Dynamic Variables under Epic/Story structure.

* JQL Criteria for creating Stories under Epic.

* Changing the order how the users and groups from Availability Settings are interpreted.

The following bugs have been fixed:

* Issue Template incompatibility with Structure.

* Custom Field "Checklist" didn't work with the function "Apply Template".

* Multi-line text custom fields using wiki renderer didn't work correctly.

* Problems with applying custom field Customer Request Type.

* Unable to clone the values in "Scope" and "Stages" when cloning a sub-tasks template.

The following improvements have been made:* Compatibility with Jira 8.4 has been added.* Support for Dynamic Variables under Epic/Story structure.* JQL Criteria for creating Stories under Epic. * Changing the order how the users and groups from Availability Settings are interpreted.The following bugs have been fixed:* Issue Template incompatibility with Structure.* Custom Field "Checklist" didn't work with the function "Apply Template".* Multi-line text custom fields using wiki renderer didn't work correctly.* Problems with applying custom field Customer Request Type.* Unable to clone the values in "Scope" and "Stages" when cloning a sub-tasks template.

The following bugs have been fixed: - Problem with creating issues when Create Criteria Query was defined in the sub-task template. - Dynamic variables didn't work in Jira 8.0.

The following improvement has been made:

• Support for fields: Original Estimate, Remaining Estimate, Security level .

The following bugs have been fixed:

• Template's name wasn't visible on the view issue screen.
• While using a template to create issues with links, the newly created issues were linked correctly between each other, but also got additional links to the issue in the TEMP project.

The following improvements have been made:

• NEW feature: Default templates for Jira and for Jira Service Desk.
• Support for Request Participants and Customer Request Type custom field .
• Performance improvements.

The following bugs have been fixed:

• Drop down list with templates was hidden on the Customer Portal after coming back to the request form.
• Component/s couldn't be copied from Task/Story to Sub-task using alternative source.
• Web links and Component/s couldn't be copied to Sub-task.
• Problem with Checklists for Jira app.

The following improvements have been made: * New JQL searcher has been added: issue in templateForIssue("issueKey"). It allows to find a template from which selected issue was created . * New JQL searcher has been added: issue in searchTemplates("", ""). It allows to find templates with selected attributes, such as templateName, category, projectAvailability etc. The following bugs have been fixed: * Epic creation was disabled when components were aded to the scope. * JQL on sub-task creation didn't work with using Apply template feature.

The following bugs have been fixed: * Wrong link to the documentation in the variables configuration. * JQL condition on sub-task couldn't be saved. * Using 'mailto' in the description on the create template screen didn't work. * Problem with $PARENT_COMPONENTS variable.

Changes connected with rebranding Intenso to Deviniti

New features have been added: * The small Issue Templates panel on the template has been added. It includes links to the configuration and to Scopes (for admins), information about template's status (enable/disable), number of issues created from the current template and a list with 5 last created issues. * Default scope for sub-tasks. The following bugs have been fixed: * Problem with translation of Select template custom field on Customer Portal in French language. * Creation error using the feature 'Use as a template' for issue type Epic. * Keys appear instead of labels in case of languages which weren't added to the intl_data.json * Static variable $PARENT_LABEL (in sub-task) didn't work in case of more than one label in the parent issue.

We have fixed several issues in this release

The 6.5.0 version brings many new features and changes like Alternative Source, Sample Templates or Events Log. Please read the full release notes here: https://intenso.atlassian.net/wiki/display/IT/Issue+Templates+6.5.0

To read full release notes click here.

Read the full release notes here

• We have added validation for scope selection on subtask level (summary field is required there)
• We have fixed issue with template selection on transition screen

Read the Release Note here.

We have fixed two issues:

• Sort order for templates is now working correctly
• The $USER_NAME variable is now working correctly

• Added templates of Epics. Read more here.
• Added support in autocomplete feature for Checklist for Jira

Read the full Release Notes here.

• New place for Scopes
• New place for Most Popular
• Assignee subtasks on parent edit
• New template has now disabled Jira Service Desk Flag by default
• Fixed issue with cloned templates
• Fixed issue with Default Template flag
• Fixed issue with execution of the same function to create new issue
• Fixed issue with disable function with subtasks

Full release notes are is here.

• You can now limit template's visibility to project categories
• We have fixed several issues

• Added version for Jira Cloud
• Added support for nFeed and Insight custom-fields to Copy feature
• Added dynamic DueDate to Copy Subtask post function
• Fixed issue with jQuery selector in Default Templates

• You can now apply template during issues import
• You can use Epic Name in autocomplete feature
• You can also get information about used template ID in Groovy script

We have fixed several bugs in this version:

• Issue with issue edit caused by ConcurrentModificationException exception
• Issue in the license checker
• Issue with nFeed customfields

Full Release Note is available here.

This version includes many changes and bugs fixing.

• Improved template's field view
• Added Template Tool panel on template issue
• It is now up to 80% faster
• Added new type of context - Users
• Bugs fixing

Read the full Release Notes.

Read the full Release Notes of the Gold Edition

Read the full Release Notes of the Gold Edition

Read the full Release Notes of the Gold Edition

Read the full Release Notes of the Gold Edition

Read the full release notes.

Read the full release notes.

• Fixed issue with templates in Customer Portal
• Fixed issue with Use as a template

• Templates Summary
• Templates Category

Read full Release Notes. This version is for Jira 7 only.

• Templates Summary
• Templates Category

Read full Release Notes. This version is for Jira 6 only.

• Support multi-context for select type of custom field

Release Notes

Release notes

Full Release Note

We have fixed a few important bugs:

• Error while creating tickets in a Kanban or Scrum Board via Agile Plugin
• Fixed problem with displaying non existing issues

Full Release Note

Release Note

Release Note

Release Note

Release Note

Release Notes

Release Note

Release Notes

• Fixed problem with select in scope

• Added post function to create issue from template. Read more.
• Added "Dynamic Variables" in subtasks and enabled it in: non-text fields: versions, assignee, reporter and custom fields: user picker, select. Read more.
• Fixed readonly field in Internet Explorer 8
• Fixed Customer Portal crash
• Fixed default checkbox on creating template

• Templates on Customer Portal - read more about our new feature!
• Added compatibility for Data Centre
• Added hidding "Templates" field for certain issue types

• Added screen context to template
• Added support for checklist
• Added hiding customfield for only one default template
• Fixed variable with space
• Fixed autocompliting assignee and reporter

• Add Custom Link to templates
• Custom fields of type "label" are not available in scope
• aui-field-something blue-bg template-background Weirdness
• Default template is not selected when clicking "Create" button from admin area
• Clear label values when we change the template

• Fix problem with hidden form

• Fix problem with edit customfield

• Stages, previously template's subtask have one stage, now may have many stages.
• Fixed creating template is 'Use as Template' feature (selection of Projects, Issue types and Languages).
• Configurable Colors under autofilled fields. Feature for user to indicate scopes when creating issue.
• Generating Support File mechanism changed (now plugin support file have also Jira Support File).
• Change configuartion views (Administration > Add-ons section) to follow AUI requirements - subsites appear on left section.
• Postfunction that disable / enable Template added.
• Scopes management improvements (field editing, comments on fields).

• Templates for autocompliting subtask

• Templates for autocopliting subtask

• Bug fixing

• Bug fixing

• Support for customfields in "Use a template"

• Support for customfields in "Use a template"

• Support for Number field
• Support for Data Time field
• Bug fixing

• Support for Number field
• Support for Data Time field
• Bug fixing

• Field read only
• Create subtask in use as template
• Fixing bug with multicontext customfield in use as template

• Field read only
• Create subtask in use as template
• Fixing bug with multicontext customfield in use as template

• Support for Multi-Level Cascading Select in post function InTENSO [Issue Templates] - Copy values

• Support for Multi-Level Cascading Select in post function InTENSO [Issue Templates] - Copy values

• Bug fixing

• Bug fixing

• Jira REST API

• Bug fixing

• Improve wizzard
• Bug fixing

• Use Jira REST API

• Bug fixing

• Improve wizzard
• Bug fixing

• Add Group Context
• Change adding new scope
• Subtasks under templates can be copy to the existing issue using apply template if postfunction copy subtask is added to workflow (create transition)
• Using template in workflow transition
• Autocomplite comment
• using variables in comment
• Fixed bug with empty assignee

• Error with autocomplite fields

• Error with copying components and labels in postfunction and in "use as a template"

• Add Group Context
• Change adding new scope
• Subtasks under templates can be copy to the existing issue using apply template if postfunction copy subtask is added to workflow (create transition)
• Using template in workflow transition
• Autocomplite comment
• using variables in comment
• Fixed bug with empty assignee

• Error with autocomplite fields
• Error with copying components and labels in postfunction and in "use as a template"

Improvements:

• Add autocomplete for subtasks

Bug fix:

• Autocomplete for users doesn't work well

Improvements:

• Add autocomplete for subtasks

Bug fix:

• Autocomplete for field Multi User Picker doesn't work

Improvements:

• Change order of available templates

Bug fix:

• Clear components field for each template change

Improvements:

• Change order of available templates

Bug fix:

• Clear components field for each template change

Bug fix:

• Autocomplete for field environment does not work
• Plugin is now working on old create issue page

Bug fix: 

• Autocomplete for field environment does not work
• Fix jEditor support for Jira 5.x

Improvements:

• Add support for Jira6!

Improvements:

• Add support for URL field
• Improve plugin speed during creating issue from template

Bug fix: 

• Clear original reporter from watch list if change it on post-function

Improvements:

• Add support for Multi Select, Security Level and reporter field
• Other small improvements and fixes

Bug fix: 

• Multi User Picker autocomplete not working properly

Bug fix: 

• Clone issue does not work anymore after enabling Issue Templates plugin

Improvements:

• Add support file generator

Improvments:

• Copy fields from template to the new issue (e.g. links and attachments)

Bug fix: 

• If no Stage defined, no subtask is created

Improvments:

• Subtasks under templates can be copy to the new issue depends on own profile (scope)
• Show list of templates for each profile

Bug Fix:

• Fix support for Assignee field

Improvments:

• Add support for Cascading Select, Group Picker, Multi Group Picker and Check Box
• Add support for Jira 5.1.x

Bug fix:

• Issue #1

Announcement

To improve usability we have decided to redesign this plugin completely. The decision has vast impact on previous version of Issue Templates, there are incompatible. If you have installed version 1.x or 2.x please contact to us directly to solve migration problem.