Publishing dates back to Jira

Drag a bar and Jira stays as it was. The move is stored in Ganttry's own storage, against your chart. The bar is drawn hatched so you can see which bars are Jira's account of the work and which are yours.

This is deliberate. You can rearrange a plan, argue with it, and throw it away without anyone else seeing a half-finished idea on their issues.

Manual moves are saved as you make them. There is no save button, and the status line reports it if a write is refused.

Publish to Jira in the toolbar opens a list of every date that differs from what Jira holds. Nothing is written until you press the button.

What is ticked when the dialog opens:

Open the dialog on a plan you have not touched and you get a list with nothing selected.

Each row shows the date it will replace, so you can see whether you are setting a date or moving one. The button carries the count: “Publish 12 dates” is a sentence you can disagree with.

The limit is 200 changes in one publish.

The caret beside the Publish button holds Undo publish. It puts every date back to what it was before the last publish. The record is kept in app storage, so it survives a reload and still works tomorrow.

⌘Z does not undo a publish. It undoes moves on the chart, which is a different thing.

Two date fields on the issues you tick, and nothing else. Every call is made as you, so your own Jira permissions decide what is allowed before Ganttry is involved.

The complete list of what this app can write to Jira, and how that is enforced, is on the security page.