Documentation
All four pages
The four things this app does that the last one you used did not.
Back to the indexReleases
Why did changing this date warn me?
Releases are Jira's fix versions. Ganttry reads them from your issues and draws each dated version as a line across the plan, with the work that belongs to it banded underneath.
Group by Release to see what ships in each one.
Changing a release date goes straight to Jira
This is the exception to everything in Publishing.
Move a bar and nothing leaves Ganttry until you publish. Change a release date and it is written to Jira immediately. Everybody reading that version sees the new date at once, including people who have never opened this chart.
That is why release dates are edited in a dialog, not by dragging, and why the dialog says so before you confirm. Open it with Plan ▸ Releases.
There is no undo. Ganttry can set the date back, but the intervening state was already visible to everyone.
Creating a version
The same dialog has a New in field. Pick a project, name the version, and it exists in Jira as soon as you confirm.
What Ganttry will not do
- It cannot delete a version. A version with issues in it cannot be removed without deciding what happens to them.
- It cannot mark a version released or archived.
Both are done in Jira's own project settings.
Every call is made as you, so a planner who can see several projects and administer one of them can change dates in exactly that one, and Jira's history records who did it.