Reference
Permissions and data
Built on Atlassian Forge. The criteria live on the issues in your Jira site; nothing leaves Atlassian.
What the app stores
- On each issue, as a Jira issue property (
featurebridge-ac): the criteria (text, Given/When/Then steps, status, when the status last changed) and the counts Jira indexes for JQL and the workflow validator. - In the app's Forge storage for your site: templates (names and criteria) and the default-template rules (project, issue type, template).
The app stores no Atlassian account IDs, names or e-mail addresses: it does not record who ticked a criterion off (Jira's own issue history is not changed either). There is no YTI server; we cannot see your criteria or templates.
How it reads and writes
- The editor reads and saves criteria as the signed-in person, so Jira decides what they may see and change. Editing needs the Edit issues permission.
- The only thing the app does on its own is put a default template on a newly created issue, when a Jira administrator has set a rule for it.
- The settings page (templates, default rules) is for Jira administrators.
Jira scopes
| Scope | Used for |
|---|---|
read:jira-work | Reading the issue's criteria and summary, checking the person's permission to edit the issue, listing projects and issue types for the default rules |
write:jira-work | Saving the criteria as the issue property |
storage:app | Templates and default-template rules |
Where data goes
Nowhere outside Atlassian. The app makes no requests to the internet and has no servers of its own, so it qualifies for Atlassian's Runs on Atlassian program. Forge keeps technical logs for the app; the app writes only error messages there, never criteria text, issue summaries or names.
After uninstall
Atlassian deletes the app's Forge storage (templates and default rules) according to the Forge data retention policy.
Price
Free for every team, without a user limit.
See also the Privacy Policy and Terms of Service.