Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to autosave description

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


3 answers

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.

0 votes
iDa Khoshvaght
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 18, 2023

Hello @appsmobiliojivisata and other folks here,

We do have an open feature request for it here:

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.

0 votes
Callum Carlile _Automation Consultants_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 25, 2021

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:

2021-06-25 16_17_18-[TEST-5] test 2 - Jira.png

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

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jun 25, 2021

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,


Callum Carlile _Automation Consultants_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 28, 2021

@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!

@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.



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

Like # people like this

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.

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.

Like # people like this

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events