Auto-saving for Comments would speed up processing and make it more reliable, as saving cannot be forgotten, The same applies to Description and Summary.

Watchers of this issue may be interested in these related feature requests:

• JRACLOUD-4233 – It would be nice to be able to save issues as "draft"
• JRACLOUD-74735 – Ability to see all unsaved comments.

Yes, Anusha that DOES indeed look like the same topic. Thank you!

Hey 9faa6e3b5124 thanks for your response!

Can I confirm, was this an issue (of type Story) to which you had added a bunch of details on the Create issue screen? And because you hadn't clicked the Create button yet when the browser crashed, you essentially lost a draft issue? If so, I think this ticket might be a match for what you're after: JRACLOUD-4233 – It would be nice to be able to save issues as "draft"

Yes, comments now save (thank you!!) – but I would say (as I was burned by this not too long ago) that the ability to auto-save/have drafts of NEW stories (etc) would be extremely helpful and is still needed!

I had story that I was building out that had a lot of detail/links and before I submitted it, I had to force quit my browser.
I lost everything.
I recognize though it might not be possible, so maybe I just build that section elsewhere and copy/paste it in when ready.

Thanks!

Can the watchers of this issue clarify what the current ask is as I believe the behaviour has changed since this ticket was first created. Comments do in fact autosave; for example, you can go to the full issue page (browse/issue-key) and start typing a comment and don't click Save. Then navigate to a different page. If you then open up that issue again, you will see your comment draft.

In order to remove this draft state, you need to press Save or Cancel.

Not only with comments as stated in this issue, but I have similarly experienced losing work logs as well.  Very frustrating.  I have created a similar issue as this issue but for work logs here: https://jira.atlassian.com/browse/JRACLOUD-77504

👋
The new issue view in Jira cloud offers a draft state for the rich text editor locations in the issue (Description, comments, and custom fields) The draft will be maintained until you save it or discard it.

Hi, there.

We need it very much in our work. Please, rise up the priority of this health-saving feature.

Yes, please. Accidentally losing your comments is annoying as hell. This issue was created over 10 years ago, any chance it can be prioritized?

My case is that I wrote a comment, accidentally navigated away from the page, and when I returned the comment was gone. A standard popup warning me that I'm about to navigate away from the page and I would lose my data would also work in my case, and is something I feel should be in other forms, like the issue creation page as well. FYI (in case this is something that's supposed to work already), we're running jira v6.3.15 and my browser is Firefox 48.0.2.

This is a problem for some of our users as well. Hopefully an auto-save feature will be enabled in the next release.

After just loosing my big comment on a JIRA issue, this would really have saved my day...

The auto-save feature in Confluence works great. I'd love to see this replicated in JIRA!

Rather than a big editor change, I'd be happy with a relatively simple modification that saves edited comments as drafts every minute or two, indicates a saved draft with a "continue draft comment" link, and pops the draft with a keep or kill message on a (new) create comment click. Comments are forgotten when an issue has moved on or closed so can be assumed no longer relevant after a configurable time like a couple of weeks so can be simply dropped. Keep all the action in the relevant issue screen, no need for a drafts page, etc.

This would handle the common accidentally closed tab, connection droppout, or session timeout scenarios that amount to 95% of the problem with very little work.

Hi Ganesh,

At the moment, due to a large number of other popular feature requests that are taking up significant resources, we are not looking at address this issue.

Cheers,
Anton

Could somebody from Atlassian kindly comment if this issue might be addressed in any of the future releases? Thanks.

This would be my most desired Jira enhancement.

This would be a really useful feature not only in the comments but also when creating an issue for the Description field and other fields.

Hi Dylan,

I hope you seriously consider incorporating the Confluence editor into Jira. Since the day I installed 3.4, although I myself is a big fan of wiki and encouraged people to use it, most users avoided using it. Having a real editor would definitely ease the pain. Keeping the comments safe from crashes of course is a big plus

Ahmet

Hi Ahmet,
This is a cool idea and certainly the plugable renderers we added in 3.4 would allow you to do this. Perhaps when/if we snag the wysiwig editor from Confluence we can look at implementing this as well.
Dylan