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.
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.
@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!
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.
** I noticed I just repeat some of the things Bill mentioned, but going to comment again anyway **
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.
👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events