Guides for Jira teams

Guide · Connect end of support

Gantt Cloud by WISOFT: where your start dates are

Many Jira Gantt apps keep dates in Jira fields, so switching apps loses little. Gantt Cloud by WISOFT, by default, does not. Check this before you plan your move, while the old chart still works.

We make a competing app, YTI Gantt, so we installed Gantt Cloud 1.2.10-AC on a test site in October 2026 to see what a team could take with them. Everything below comes from that test. WISOFT knows its own app better than we do, so ask them too: they may offer something we could not find.

Why this matters now

Gantt Cloud is a Connect app. Atlassian ends support for Connect on 31 January 2027, and after that Connect apps may stop working as the platform changes. We don't know WISOFT's plans. If you depend on the chart, it is safer to know where your plan is before that date.

Check where your start dates are

  1. Open the settings of Gantt Cloud

    Look at the Jira integration settings.

  2. Find “Start dates stored by Add-on”

    It was on by default on our site. If it is on, your start dates are on WISOFT's server, not in Jira. If it is off and a Jira date field is chosen, your start dates are in that field, and you can skip the warning below.

  3. Test it on one issue

    Move a bar in the chart, then open the issue. With the default setting nothing changes on the issue, not even its last updated time. Jira does not know the new start date.

What stays and what doesn't

  • Dependencies stay. They are ordinary Jira issue links, Blocks unless you chose another type. Any other app can read them.
  • Estimates and Due dates stay. They are Jira fields. In Gantt Cloud the length of a bar comes from the time estimate and your hours per day, so the end of a bar is not saved anywhere in Jira.
  • Stored start dates don't move by themselves. The toolbar button prints the chart. We found no data export.
  • Saved charts and filters are in the app, so you recreate them in the next one.

Changing the setting does not copy your dates

If you switch Gantt Cloud to a Jira date field, it does not write the stored dates into that field. The chart simply starts showing what the field holds, which on most issues is nothing. Print the chart before you change this setting. We did not test whether switching back restores everything.

How to keep your plan

  1. Print each plan to PDF now

    Use the print button in the Gantt Cloud toolbar and choose Save as PDF, once per plan you care about. It is a picture, not data, but it is your record of the plan.

  2. Pick the issues whose dates really matter

    Usually the current and next release. Old dates rarely need saving, and a long plan is quicker to schedule again than to copy.

  3. Put those start dates in a Jira date field

    Enter them by hand from the PDF, for example in Start date or Target start. Now they belong to your site, and every app can read them.

  4. Keep Due date as your deadline

    In Gantt Cloud, Due date is only a marker unless you ticked “Use due dates as task's end dates”. Many other apps use it as the end of the bar, and moving a bar then changes your deadline. In the next app, consider a separate end field such as Target end.

  5. Try the next app before you uninstall

    Install it next to Gantt Cloud and compare one project. Check that it has your hours per day, because that decides how long bars built from estimates become.

Choosing what comes next

The general checklist is in Moving off a Connect Gantt app, and Gantt chart options in Jira Cloud compares the kinds of tools. For this move, one question matters most: does the app keep your dates in Jira fields? If it does, you won't face this problem again.

Our own app, YTI Gantt for Jira, works that way and is built on Forge. At the time of writing it is waiting for Marketplace approval. If you are moving off Gantt Cloud and want to know whether it fits, write to support@yti.digital.