Reference
Permissions, data and licensing
Permissions
| Action | Who can do it |
|---|---|
| See scenarios and results on an issue | Anyone who can view the issue |
| Edit and save scenarios, resolve sync conflicts | Users with the Jira Edit issues permission on the issue |
| See the project overview | Everyone in the project; it lists only issues they can see |
| Connect Git, create the CI key, import | Jira administrators |
What is stored, and where
- In your Jira site's Forge storage (hosted by Atlassian, data-residency enabled): scenario text and its versions, the Atlassian account ID of each editor, sync state per issue, test results, and the Git settings.
- In Forge secret storage: the Git access token, the webhook secret and the CI upload key.
- In your Git repository: the
.featurefiles. They are sent only to the repository your administrator connects.
We (YTI Digital) run no servers for the app and have no copy of your data. There is no third-party analytics or tracking; we only see anonymous counts of events per site (for example, saves and syncs) in Atlassian's developer console. Closed Atlassian accounts are anonymised every week. Details: Privacy Policy.
Licensing
- Free on Jira sites with up to 10 users.
- Larger sites pay per user through the Atlassian Marketplace; see the prices on the listing.
- If a licence lapses, scenarios stay readable. Editing, sync and uploads resume when it is active again.
Terms: Terms of Service.