- Get started
- About
- First steps
- Glossary
- Migration
- Configuration
- Global configuration
- Repository
- Template configuration
- Template scope
- Manage templates
- Supported fields
- Permissions
- Using templates
- Create issue from template
- Create issue structures
- Apply template to existing issue
- Recreate issue
- Use template custom field on issue create screen
- Default templates
- Direct link
- JQL searchers
- Variables
- Static variables
- Dynamic variables
- Smart defaults
- Basics
- Smart issues
- Smart users
- Smart dates
- Smart project
- How to use smart defaults
- App Integrations
- Team-managed projects
- Jira Software
- Jira Service Management
- Advanced Roadmaps
- Issue Checklist for Jira
- Advanced
- Automation
- Legacy automation action
- REST API
- Create issue and apply template with Jira REST API
- Security
- Security statement
- App permissions
Jira Service Management
This chapter provides information about using Issue Templates for Jira app in Jira Service Management projects.
Apps can’t interfere with the form displayed in the Customer Portal. There is no API that allows apps to react to selection changes or pre-populate form with default values.
Some apps try to build the form from scratch, but it’s out of the ITC scope. Therefore, a template in the customer portal can be only applied after the request creation.
To enable applying templates on the customer portal requests turn the toggle on in the global configuration.
Template field on the Customer Portal
Template field added to the Request Type
The Template field can be added to Request Type and be selected by customers on the Customer Portal. The undoubted advantage of this solution is a quick request creation and ability to adjust the template to customer’s problem. However, it can be problematic for both Agents and Customers.
To begin with, customer sees all templates available in Templates Repository without knowing which fields will be copied to his request. It may happen that completed fields will be overwritten by those from the template. As a result, Agents won’t have a complex, detailed description of Customer’s request. What’s more, the amount of templates may be confusing. Customer can choose a template that does not fully correspond to the problem.
Hidden Template field with default template
It’s also possible to hide Template field and set the default template for target Request Types. With this configuration previously selected, default template will be applied to a request right after its creation.
It means that Customers won’t have a chance to choose a template, but as soon as they create a Request on the Customer Portal, one of them will be applied.
If the Administrator or Agent (with appropriate permissions) will set the Scope correctly, fields completed by Customer won’t be overwritten by template one’s.
For more instructions on how to set the default template in target request type, click here.
Apply template post function
You can also use the Apply template post function. It automatically completes fields with values from template after the transition is performed. For further information, navigate to Apply template post function chapter.
