Change history and backups

What Change history records#

Ganttry keeps each chart's shared plan data in its own storage: where bars sit on Main and on every branch, baselines, notes, calendars and settings. Every save that changes this data adds an entry with the person's Jira name and avatar and the time in UTC. A save that changes nothing adds no entry.

The latest 200 changes of each chart are kept, and older ones are deleted automatically.

• Private notes and note replies never appear.
• Moving, resizing or recolouring a note adds no entry; creating, deleting and editing one does.
• Changes written to Jira, such as published dates, status and assignee, are kept in Jira's own issue history.

Open Change history#

1. Open Plan insights from its tab at the right edge of the chart.
2. Choose Change history.
3. Read the entries, newest first under a heading for each UTC day. Each shows the area that changed, a summary, who made it and when.

Find a change#

• Search changes narrows the list by text.
• The category list shows All changes, or only Schedule, Capacity, Structure or Governance.
• The list updates by itself after each shared save and briefly highlights the new entry. Refresh reloads it.

See what changed#

Click an entry to open it. A schedule change lists each issue with its key, summary, start date, finish and duration, the old value struck through above the new one. Other changes list each field before and after. A long change shows its first rows and how many more there are.

Locate task beside an issue finds it on the chart. If a filter hides it, Ganttry says so.

When the details of a change were too large to store, the entry says that the plan was saved without them. Such an entry has no details and cannot be restored.

Restore a change#

Restoring puts back the values a change saved, for the items it touched. Work on anything else is kept.

1. Open the entry in Change history.
2. Choose Restore this change.
3. Read the dialog and choose Yes, restore, or No to leave the plan as it is.
4. The chart reloads with the restored data. The restore itself appears as a new entry, and Jira issues are not changed.

Undo, reset or restore#

Ganttry has several ways back. None of them changes Jira.

Reset changes#

Plan → Reset changes, the Reset button at the foot of the menu, clears every bar placed by hand in the plan you are on, Main or a branch. Ganttry then schedules that plan again from Jira dates, estimates and links. Undo brings the placements back.

It is available when the plan has manual changes and the whole plan has loaded. To reset a single issue, open its row menu and choose Reset dates; an issue you placed from no dates offers Remove from timeline instead. With several rows selected, the menu offers Reset dates on ….

Back up a chart#

A backup is a JSON file of one chart's planning data that you keep yourself. Take one before large changes, before restoring an older one, and before uninstalling Ganttry: uninstalling deletes everything Ganttry stores, and reinstalling does not bring it back.

1. Open Plan and choose Backups at the foot of the menu.
2. In Back up this chart, choose Download a backup.
3. Keep the file somewhere safe.

What a backup holds#

A backup holds only the rows for issues you can see in Jira.

Restore a backup#

1. Open Plan → Backups.
2. Choose Restore from a file and pick the backup file.
3. Ganttry writes every part of the file it can read, reports how many parts it restored and which it could not read, and reloads the chart.

• A restore replaces the chart's data with the parts in the file. Download a fresh backup first if you may want to go back.
• A file taken from another chart is restored into the open chart, and the report names both charts.
• Each restore is recorded in the plan's audit log. Jira issues are not changed.

Permissions#

• Anyone who can open the chart can read Change history. Details about issues hidden from you by Jira issue security are left out.
• Restoring a change and resetting changes need Edit Issues and Schedule Issues in every project on the chart. Only Jira administrators can restore automation and plan policy changes.
• Anyone who can open the chart can download a backup. Restore from a file needs Jira administration or project administration in every project on the chart. Download configuration and Review configuration file are for Jira administrators.
• A site policy can turn chart backups off. In the Confluence macro, Change history is read-only.