Ticket didn't save? Magically doesn't exist?

[Elena Williams]

Using Jira "Classic software" instance in Chrome spent maybe 5 minutes writing a new ticket, added small code blob and some discussion and examples.

Hit save, the ticket modal disappeared as expected.

Now I can't find the ticket. 

It's not listed in backlog.

Refreshed and searched "recent".

Searching for distinctive term in title and description doesn't find it.

Seems as though it's just gone.

---

Is this "a thing"?

Is Jira delicate now like hotmail in the 90s where you have to carefully keep your work-in-progress -- to *not* use the built in WYSIWIG because sometimes you'll just lose your work?

Searching on this forum suggests that sometimes this just might happen. The comments from Sep last year here seem to share my current feels: https://community.atlassian.com/t5/Jira-questions/JIRA-auto-save-issue-draft/qaq-p/148594  (thanks to @sfollen and @Ben Schulz for their input).

Can somebody help me confirm this either way so I can adapt my workflow? I'm angry about having to reconstruct this ticket. I honestly thought this kind of things was impossible these days, but there you go.

---

One of the most problematic things here is that I only know it's gone because I double checked in that minute.

It's entirely possible that I would have moved on and come back later and not been able to find this ticket .. and just felt gas-lit, frustrated and disempowered.

[nathan briggs]

im literally SCOURING the net for ANSWERS as to HOW TO TRICK JIRA.. into operating like it once did.. and provided me VALUE

forums.. filled w USERs.. STRUGGLING to find VALUE.. in a once useful application suite..

NOW.. IF YOU HAVE TO EXPLAIN SHT.. THEN YOU FAILED!!!!

I literally sat down to MAKE A TICKET.. somethign I can do quickly.. UNTIL YOU!

NOW.. Saving.. nope
Formatting.. nope.. cant cant cant

YOU CANT DO SHT. Literally MORE CANT than CAN

And you idiots see no problem.. and offer the age old.. Its you browser.. LOLOL... 

run.. dont walk.. OFF A SHORT PIER.

[Petter Gonçalves]

Hello @Elena Williams

Sorry to hear you are facing a bad experience while creating tickets in Jira. Please, allow me to provide you with some details and concepts so we can confirm we are on the same page here:

I can confirm to you that it is not a common problem in Jira to don't save a ticket when you have clearly clicked to save it. In other words, the background index of Jira does not have the behavior to simply ignore your request without returning any error logs with the reason and the text you just added to it and I never saw any reports of such behavior before.

That being said, If no errors were returned and the issue was not created, I'm afraid your issue was caused by an external problem (E.g: browser cache) and I completely agree with you that we have a big room for improvement here when we talk about auto-save functionality. We understand how this functionality would be useful to prevent external problems to make you lose your data (E.g.: electricity down, workstation reboot, browser crash), so we created the following feature requests to get this implemented:

Auto-save comments 

Issue draft - add autosaving of the issue before creation 

Please, vote and watch the suggestion to increase its priority and also receive notifications about any updates.

Coming back to the problem you faced, I suggest you follow the steps below to properly prevent it and collect the information we need to further troubleshoot it:

1. Clear your browser data and make sure you are using an updated version of Chrome, as described in the documentation below:
   Supported browsers 
2. If possible, install a browser extension or app to save the text you are typing or use a draft app (Word, Notes, Sublime, etc) to write long texts before posting. A good free option (I use it myself) for Chrome would be Typio form recovery app. that keeps a short memory with the last texts you typed.
3. If the problem happens again, please make sure to collect the time it happened and the details of your issue (Summary, description, etc), so we can further investigate the logs and confirm if there's something new in the application background that could be causing that

Let us know if you have any questions.