nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA auto save issue draft

KP11

Sometimes with browser issues or time outs, a user has been typing a lot of data when his browser crashes when trying to save. Is there a auto recover feature or auto save feature to prevent loss of data? I know Confluence has one. Any option to turn on in JIRA?

Accepted answers

Renjith Pillai

While this is not a JIRA solution, the Chrome add-on lazarus is very handy - https://chrome.google.com/webstore/detail/lazarus-form-recovery/loljledaigphbcpfhfmgopdkppkifgno?hl=en

All comments

Renjith Pillai

While this is not a JIRA solution, the Chrome add-on lazarus is very handy - https://chrome.google.com/webstore/detail/lazarus-form-recovery/loljledaigphbcpfhfmgopdkppkifgno?hl=en

Ben Schutz

This addon no longer exists.

I think this needs to be reopened. In terms of the amount of complex content that you might be writing on ticket creation, I think this needs to be looked at seriously.

Drew Bartlett_9u4ba5

I agree with Ben... this is a feature I need as well. I have been frustrated many times trying to write complex tickets, getting pulled away and trying to come back to it, just to have Jira having "refreshed" and losing my work.

Ben Schutz

Ok got some good news on this one. The auto save ability is partial there with the release of the brand new issue UI. So if you view an existing issue on the backlog or on the issue's own screen, you can enter content in the description field and it will be auto saved in a "draft" update. You can close the tab/browser/computer and that draft content will be there when you go to edit the description next time. It only becomes published when you hit "Save"

Image 2019-07-19 at 11.44.41 am.png Image 2019-07-19 at 11.45.05 am.png

The trick for now is to create a basic ticket, and then edit it via the new UI when adding the detailed info so that it auto saves in case something interferes with your work. Again, hit "Save" to publish.

I think their decision to only have auto save here for now is that;

it's their new UI so makes sense to put any enhancements there; and
they don't need to add any UI to manage drafts version, like a "draft issue creation section", because you can just go back to edit the existing issue description to see the draft content.

sfollen

Good idea about creating a basic ticket to take notes on. Wish I'd thought of that before Windows restarted my computer and I lost 4 very complex tickets that I was compiling data for...

Ben Schutz

That's sounds horrible

Jira should have been there for you. I suspect/hope the new experience is coming for creating tickets too, but auto-save is way overdue for a product of this maturity.

The other limitation I've found is that the new issue experience is really still in beta, so you will have to decide between losing some traditional functionality and gaining auto-save on edited descriptions. For instance, you can't (yet) insert an image into the description that is already uploaded to the ticket, you have to re-upload and insert at the same time.

(also; Windows update force reset sucks)

sfollen

Oh, the number of times I have had to refresh the screen and delete and reinsert images... I don't even try to save tickets anymore; when I finish the description (which always takes forever because I am back and forth between 20 things), I just copy the whole thing, refresh the screen, paste over whatever is there when the screen refreshes, delete the non-images and then reinsert. Seems like a lot now that I am writing it all out...

And by the way, even though your suggestion was a great one, I've turned to the very modern technological fix of drafting myself an email and keeping notes in there about any tickets I need to raise. (Gmail does such a great job with autosave.) Works fine and allows me to be suitably distracted all the time, but it does remind me of 20 years ago when I used to email myself things in order to save them or pass them between computers. Ahh, technology.

Totally, totally with you on the forced reset

Maximilian Porzelt

There is a jira app on marketplace that does the trick for comments - saving issue descriptions as draft is coming soon:

https://marketplace.atlassian.com/apps/1223509/autosave

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

draft