Reference
Permissions, data, licensing
The plan lives in Jira
Dates are the issues' own date fields and dependencies are Jira issue links. The app does not keep a copy of your issues: every chart is read from Jira when it opens, as the person opening it.
What the app stores
In Atlassian's Forge storage for your site, only what Jira has no place for:
- Dependency type and lag per Jira link ID, when a link is not a plain finish-to-start.
- Baselines: a name, the date it was saved, and start and end dates per issue ID.
- Saved views: name, JQL filter, zoom, grouping, colors and options.
- Settings: field IDs, link type names, working days and holidays.
It stores no Atlassian account IDs, no names or e-mail addresses and no issue summaries or descriptions. View and baseline names are whatever your team types.
What it reads and writes in Jira
- Reads: issues matching the plan's JQL (summary, type, status, assignee, parent, priority, the two date fields, time tracking and issue links), the person's project permissions, fields and link types, the project's releases and the sprints of its Scrum boards. In the details panel, also the issue's workflow steps and the people it can be assigned to (searched as you type, never stored).
- Writes, only when someone changes the plan: the start and end date fields, issue links (create and delete), and from the details panel the issue's summary, assignee and status (a workflow step).
- Issues are viewed and created in Jira's own issue view and create dialog.
- The Rovo agent (YTI Gantt planner), when someone asks it: reads the plan as that person and gives Rovo the keys, summaries, statuses, assignees and dates it needs to answer; it moves an issue or creates a drafted plan only after they confirm.
All of this runs as the signed-in person, so Jira's permissions apply and Jira's history shows who changed what.
Where data goes
Nowhere outside Atlassian. The app has no servers of its own, makes no requests to the internet and qualifies for Atlassian's Runs on Atlassian program. YTI Digital cannot see your plans.
Forge scopes
| Scope | Used for |
|---|---|
read:jira-work | Searching the plan's issues, permissions, fields, link types and workflow steps |
read:jira-user | Finding the people an issue can be assigned to, in the details panel |
write:jira-work | Writing dates, summary, assignee and status; creating or deleting issue links |
storage:app | Baselines, views, dependency types and lag, settings |
read:project:jira | Finding the project's boards |
read:board-scope:jira-software | Reading the project's Scrum boards |
read:sprint:jira-software | Sprint names and dates for the sprint lane |
Licensing
Free for up to 10 users; above that, billed per user by Atlassian through the Marketplace. With an inactive licence the chart stays readable, but dates, dependencies and settings cannot be changed and no new views or baselines can be saved.
See also the Privacy Policy and Terms of Service.