- Global configuration
- Template configuration
- Template scope
- Manage templates
- Supported fields
- 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
- App Integrations
- Team-managed projects
- Jira Software
- Jira Service Management
- Advanced Roadmaps
- Issue Checklist for Jira
- Legacy automation action
- REST API
- Create issue and apply template with Jira REST API
There is no data from Jira stored on the app’s server. The only record stored on the app’s server are installation details received during installation process, which is common practice for all Connect apps (apps for Jira Cloud) and token data. Token data includes user account ID saved in the database when you create a REST API token.
For details go to the Privacy & Security tab on the Atlassian Marketplace.
Issue Templates Cloud stores REST API token configuration with user account ID.
Personal data received by
/rest/api/2/user may be processed. This includes:
- display name of a user
- time zone and email address - only if a user allows it in their account settings
Above data may be processed in order to edit an issue and fill in issues fields, for example, description.
Our app stores information depending on the country where the Jira server is located. Data residency is selected at the moment of installation. For now, it’s not possible to transfer data after installation (despite changing Jira’s data residency).
We currently support two locations, US and EU with the following app URLs:
Follow the official Jira roadmap for more information about support for full data residency in Jira apps.
End user data is shared with the following third-party entities, depending on data residency:
|BetterStack (formerly Logtail)||Germany|
|Heroku||United States of America|
|Papertrail||United States of America|