How to autosave description

[appsmobiliojivisata]

Sometimes i write description and forget to save it. How to autosave description when i'm moving to another page or issue? I don't need save button

[Ian Hamilton]

Personally, I'd like the option to just auto-save I can't tell you how many times myself or one of my teammates just forgot to save.

I understand some folks would like to draft up things and consciously hit save once they are ready.  But it sure would be nice to have a configuration for people like me to just go ahead + auto save.

[Matthias Weidner]

We edit a lot together in issues. And apart from not saving, another problem permanently occurs: User A opens and edits an issue, user B opens it too (user A has neither saved or closed anything), user A saves and closes, user B (who didnt even see user A's additions) saves and closes and deletes what user A had added. Embarrasing. Issues should either be blocked for editing (viewing is fine) when someone else is editing it. Or be editable by multiple users (that would we super great ;)

Plus autosave, of course.

[Bill Sheboy]

Hi @Matthias Weidner -- Welcome to the Atlassian Community!

There is another symptom to watch for: unsaved draft changes. 

We had a user make changes to an issue's Description, edit the field without saving, and move on to other things.  Weeks later...they edited the issue again, saving their changes and walking over prior edits.  There is now a indicator for "unsaved changes", although it is not highly visible, IMHO, as only the person with the unsaved changes can see the prompt.

Kind regards,
Bill

[iDa Khoshvaght]

Hello @appsmobiliojivisata and other folks here,

We do have an open feature request for it here:

• JRACLOUD-76121: Auto-saving the Description in new issue view

We suggest you add yourself as a watcher on that page to follow up on its progress and hit the “Vote for this issue” button to help raise its visibility within our Development and Product Management teams.

It's highly appreciated if you can share how this is affected you or your team in the comment section of that feature request.

[Callum Carlile _Automation Consultants_]

Hi @appsmobiliojivisata ,

It should already do this. Even if you close the tab and return to the issue later on, the changes you make should still be retained, and you might see something like this:

[appsmobiliojivisata]

I see on you screenshot that they unsaved. So other users won't see your changes)

[Bill Sheboy]

Hi @appsmobiliojivisata 

No, other users will not see the unsaved changes, and this is a behavior/problem to watch for in the new issue view...

We recently had one user edit a field, click elsewhere on the page, and that resulted in unsaved changes.  Those changes stuck around for over a month in the cloud...eventually when saved, it replaced subsequent edits by other users.  Luckily we could see the changes in history and re-implement them.

One lesson: always select save or cancel for description changes on the new issue view.

Best regards,

Bill

[Callum Carlile _Automation Consultants_]

@appsmobiliojivisata The functionality is the intended design, as you may start to make some notes but don't yet want them to be saved/published, so that is why there is this concept of the 'unsaved draft'. But do watch out for what @Bill Sheboy has described as this could definitely catch people out!

[Donatello Nguyen]

@Callum Carlile _Automation Consultants_ 

I understand this is an intended design, I have a case where I lost all of my draft somehow, perhaps another user tries to edit the same description later and overwritten my draft description (have not tested this). 

Second part is that the save button is located at the bottom of the description.  The description can be lengthy which the user can easily missed the save button if they're editing in the middle it.

If the save button is fixed/sticky on the top right corner while the description, that will solve some of the issue above; or if the description auto-save that will prevent the issue as well.

Another issue w/ draft feature is that the user doesn't know which jira task is under "draft" and thought the description was saved.  It isn't until later along the line the developer mentioned he/she couldn't work on it because there's not enough info.  

Please see if there's anything you can do to improve the UX part for this; it doesn't happen all the time, but when it does, it's frustrating.

Thanks

** I noticed I just repeat some of the things Bill mentioned, but going to comment again anyway **

[Patrick T Chaopricha]

I totally agree with having the sticky save button at the top or something that reminds me I need to keep.  I just lost a lot of information I typed in and didn't click save before clicking somewhere else.  The "Unsaved" version didn't show up, so everything was wiped out.  So frustrating.

[Salih Mutlu]

It is just annoying to lose all written description just because of not having autosave which I encountered. Until published, in my opinion, changes can be held in a saved but not published state.