Data & Security
Templify reads your templates and creates work items from them, so this page answers what security and compliance teams ask first: where the data is, who can reach it, and what happens when the app is gone.
Where your data is
- Templates are your work items. A template is an ordinary work item in one of your spaces, and every work item created from it is an ordinary work item too. Both live in Jira like any other.
- Templify's own records stay inside Atlassian. Template settings, default templates, the usage history and the audit log are kept in storage that Atlassian hosts for the app, separate from every other installation.
- No servers of ours. Templify has no servers of its own and sends no data to any outside service: no analytics and no tracking. The ready-made templates in the gallery ship inside the app. Links to these docs and to our help portal open only when someone selects them.
Who can reach it
Templify checks Jira permissions and its own two global permissions before it shows a template or acts on one.
| What | Who can reach it |
|---|---|
| A template work item | Anyone who can browse its space, as with any work item |
| Creating a work item from a template | Issue Templates - Use Templates or Manage Templates, and Create work items in the target space, where the template is available |
| Jira's Create dialog filling in a template | Issue Templates - Use Templates; only templates in spaces the person can browse are offered |
| Apply template on a work item | Issue Templates - Use Templates, and Edit work items on that work item |
| The Issue Templates panel: a template's settings and usage history | Issue Templates - Manage Templates and Create work items in the space; changing settings also needs Edit work items on the template |
| Apps → Issue Templates, import and export | Issue Templates - Manage Templates |
| Configuration and Audit logs (under Jira settings → Apps) | Jira admins only |
| The Automation actions | The account the rule's action runs as, with that account's Jira permissions |
Templify creates and applies templates as the person who uses it, so Jira checks that person's permissions. Some follow-up work runs as Templify itself: copying a template's files, and adding its subtasks, child work items and links after Jira's Create dialog. Templify does it only for a template that is enabled, available in the space and visible to the person who created the work item. Who has the two global permissions depends on your site: see Permissions.
What Templify records
| What | Where it shows | How long it is kept |
|---|---|---|
| Each template's settings: name, whether it is active, availability, skipped fields, dynamic fields | The template's Issue Templates panel | Until the template work item is deleted |
| Default templates, per space and work type | Set default Issue Template and Apps → Issue Templates | Until the default or the template is deleted |
| Usage history: who created from the template, when, and the key, summary and type of each work item created | The template's Issue Templates panel | Until the template work item is deleted |
| Audit log: who did what and when, for template changes, defaults, configuration, imports, and creating or applying a template (work items created in Jira's Create dialog are not logged) | Jira settings → Apps → Issue Templates → Audit logs | No automatic deletion while the app is installed |
| The app's configuration: the global repository and the spaces with the Issue Template field | Configuration | While the app is installed |
The usage history and the audit log name people by their Jira account and display name. A template work item that someone deletes takes its settings, defaults and usage history with it; its audit log entries stay.
What Templify changes in Jira
- Work items it creates or updates, always on someone's action: creating from a template, applying one, or a Jira Automation rule with a Templify action. It copies field values, attachments, subtasks, child work items and links.
- The Issue Template field. Templify's own field. On a work item created through the field, it records which template was used.
- Create screens. When a Jira admin adds a company-managed space on the Issue Template field tab, or saves a default template for it, Templify puts the Issue Template field on that space's Create screens. It does not touch screens on install.
- Jira's Create dialog. In the spaces where it is set up, Templify adds the template picker and fills the form with the default template.
- A small hidden record on each template work item, holding its name, whether it is active and its availability, so that Jira can find templates quickly.
If you uninstall Templify
The templates stay in Jira as ordinary work items, and so do the work items created from them, with their values, subtasks, child work items, links and attachments. What Templify kept for itself stops being available:
- Atlassian keeps the app's data, including template settings, default templates, the usage history and the audit log, for 28 days after an uninstall. Reinstalling Templify does not bring that data back by itself.
- Within that time, recovery is a support request that Terano Apps, as the app's vendor, raises with Atlassian. It must be raised within 21 days of the uninstall, so that it is processed before the 28 days end.
Before you uninstall
Export the templates you want to keep
On Apps → Issue Templates, export each template. The file holds its fields, structure, dynamic fields and skipped fields, and you can import it into Templify on any site. It does not hold attachments or user fields. See Import and Export Templates.
Export the audit log
Under Jira settings → Apps → Issue Templates → Audit logs, export the log as a file if your records need it.
Already uninstalled and need the data back? Contact us with the date you uninstalled.