Coming from another Gantt app

Why teams are moving now

Atlassian ends support for apps built on its older Connect platform on 31 January 2027. Several Gantt apps for Jira Cloud, among them Gantt Cloud by WISOFT, are Connect apps; Jira has started showing their users that such apps may stop working. YTI Gantt is built on Forge, Atlassian's current platform, and runs entirely on Atlassian's infrastructure.

What carries over

Dates

Most Gantt apps for Jira store an issue's dates in Jira fields, usually Start date (or a custom "Start" field) and Due date. Point YTI Gantt at the same two fields in the settings and every bar appears where it was.

Dependencies

If your old app drew dependencies as Jira issue links (often Blocks, sometimes a custom type such as "Gantt dependency"), tick that link type in the settings and say which side comes first. The arrows appear as they were, as finish-to-start links with no lag; set a different type or lag on the arrows that need it.

What does not carry over

• Anything the old app kept in its own storage rather than in Jira: baselines, saved views, its own lag values or dependencies that were never Jira links. Save a new baseline on day one so you have a reference from then on.
• Cost tracking. For people, YTI Gantt has the workload panel and Resolve overlaps, which moves double-booked work to each person's free time.

Dependencies that only the old app knows

If your old app can export the plan to Microsoft Project XML and the task names start with the issue keys (for example SHOP-12 Payment page), import that file with Export → Import from MS Project. Tasks with a key are not created again: those issues get the file's dates, and the dependencies between them become Jira issue links with their type and lag. See Import from MS Project.

Switch in five steps

1. Install YTI Gantt next to the old app

   Both can run side by side; nothing is changed until someone moves a bar.

2. Choose the fields and link types

   In the settings, pick the start and end fields and the dependency link types your old app used.

3. Open the Gantt tab of one project

   Check that the bars and arrows match the old chart. Use Plan health for dependencies the dates do not respect.

4. Save a baseline and the views you need

   For example one view per release, shared with a link.

5. Uninstall the old app

   When the team works in YTI Gantt. Your dates and links stay in Jira.

Coming from Microsoft Project

Save the plan as XML in MS Project and choose Export → Import from MS Project on the Gantt tab: the tasks become epics, issues and subtasks with their dates and dependencies. See Import from MS Project.