Privacy Policy

YTI Gantt for Jira is a Jira Cloud app built on Atlassian Forge by YTI Digital OÜ (Estonia). It shows the issues of a Jira project on a Gantt chart and lets people change their dates and dependencies. Contact: support@yti.digital.

You (your organisation) decide what is planned in your Jira site and who may see and change it. For the Jira data the app reads on your behalf, you are the controller and the app only processes it to show and change it in your Jira site.

What the app stores

In Atlassian's Forge storage for your site:

• Dependency details: the type (for example start-to-start) and lag in working days of Jira issue links, by link ID, when a link is not a plain finish-to-start.
• Baselines: a name, when it was saved, and a start and end date per Jira issue ID.
• Saved views: a name, a JQL filter and display options (zoom, grouping, colors, options, the baseline shown).
• Settings: which date fields and link types the chart uses, working days and holidays.

In your own browser the app keeps only the ID of the view you last opened in each project, so the chart opens with it again.

The app stores no Atlassian account IDs, no names or e-mail addresses and no issue content. Names of views and baselines are whatever your team types; please do not put personal data in them.

What the app reads and changes

• Reads from Jira, as the signed-in person: the issues of the plan (summary, type, status, assignee, parent, priority, the chosen date fields, time tracking, story points and issue links), that person's project permissions, the site's fields, link types and issue types, the project's releases and the sprints of its Scrum boards (names and dates), an issue's workflow steps, and the people an issue can be assigned to when that person searches for an assignee.
• Changes in Jira, only when that person makes a change: the chosen date fields of issues, issue links (created and deleted), and from the details panel an issue's summary, assignee, status and parent. It creates issues when that person creates them from the chart, imports a Microsoft Project file, or confirms a plan drafted by the Rovo agent.

Issue data shown on the chart is read when the chart opens and is not kept by the app.

Where data goes

• Nowhere outside Atlassian. The app has no servers of its own and makes no requests to other services.
• Nothing is sent to YTI Digital: we cannot see your plans, baselines, views or issues.
• Data is stored and processed by Atlassian (Forge), as described in Atlassian's own privacy policy.
• When someone asks the app's Rovo agent, the plan data it needs to answer (issue keys, summaries, statuses, assignees and dates) is passed to Atlassian Rovo, inside Atlassian's cloud.

Who can see the data in Jira

Everyone sees only the issues their Jira permissions allow. Saved views and baselines are shared with everyone who can open the project's chart. Changing dates and links needs the matching Jira permissions; settings are for Jira administrators.

Logs

Forge keeps technical logs for the app (for example errors). They contain no issue content and no personal data.

Retention and deletion

• Deleting a view or a baseline deletes it immediately.
• Deleting a dependency removes the Jira link and its stored type and lag.
• Uninstalling the app removes its data according to Atlassian's Forge data retention rules. Dates and links stay in Jira, where they always were.

Your rights

Everything the app keeps stays in your site's Forge storage, where YTI Digital cannot read it, so there is nothing to export or delete on our side. Questions about this policy: support@yti.digital.

Changes

We will update this page before releasing a version that stores or sends data differently.