Data and Privacy

Issue Templates & Recurring Tasks for Jira is a Forge app. It runs on Atlassian's infrastructure, and everything it stores is kept in Forge storage for your site. It calls no services outside Atlassian, which is why it is part of Atlassian's Runs on Atlassian program. Yamuno receives none of your data.

What it stores

Data	Kept until
Templates: name, summary, description, fields, child items, assignments, who created and last updated them	You delete the template
Schedules: the template, where and when they run, their options and answers	You delete the schedule
Each schedule's run history, the last 50 runs	You delete the schedule
Access settings	You change them

People are stored only as Atlassian account ids, never names or email addresses: who created and last updated templates and schedules, the people in an assignee rotation, people chosen as a template's assignee or reporter, who ran a schedule by hand, and people on the access lists. Names are looked up from Jira each time they are shown, so a renamed or closed account never lingers in the app. An @mention typed into a template's description is kept the way Jira keeps mentions.

The app doesn't copy your work items. Work it creates lives in Jira like any other work item.

Permissions it asks for

Scope	Why
read:jira-work, write:jira-work	Read work items, create them from templates, apply templates, add child items, links and failure comments
read:jira-user	Show people's names and pick assignees and reporters
read:servicedesk-request	Find portal request types for assignments
manage:jira-configuration, manage:jira-project	Register where Jira's Create dialog and the portal fill in templates, and check who is a Jira admin
storage:app	Keep templates, schedules and settings in Forge storage

Uninstalling

Uninstalling the app deletes its Forge storage from your site. Work items it created stay in Jira.