My unsaved changes are gone
How to get back changes you made in a Script Master editor but didn't save.
Symptomβ
You left an editor in Script Master without saving. When you open the item again, your changes aren't there.
You left through Jira's or Confluence's own navigationβ
Cause: Inside Script Master, Back to list asks before it leaves an editor with unsaved changes, and switching tabs keeps them. A link in Jira's or Confluence's own sidebar or header can't be stopped by a Forge app, so it leaves without asking.
Solution: Your changes are kept in that browser for 7 days.
- Open Script Master in the same browser, signed in as the same person.
- Open the tab of the item you were editing.
- On the message that starts Unsaved changes to, select Restore.
Result: The editor opens with your unsaved changes. Select Save to keep them.
The changes were made in another browser, or more than 7 days agoβ
Cause: Unsaved changes stay only in the browser where you made them, and only for 7 days.
Solution: Make the changes again. To get back an earlier saved version instead, see Version history.
Someone saved the item sinceβ
Cause: Script Master offers unsaved changes only while the saved item is the same as when you started editing. If anyone saved the item after that, or deleted it, your changes aren't offered, so they can't overwrite the newer version.
Solution: Open the item and make your changes again on top of the saved version. To see what the other person changed, see Version history.
You edited another item of the same kindβ
Cause: Each browser keeps one set of unsaved changes per kind of item, for example one for fragments and one for web triggers. Editing another fragment without saving replaces the unsaved changes of the first one.
Solution: Make the changes again. Save an item before you start editing another one of the same kind.
Relatedβ
- Navigate the admin page: tabs, page URLs and unsaved changes.
- Known limitations: what Script Master can't do.