History and Markdown

[Mark Greenwood]

Looks like this has been asked before but I'll ask again in the hope that someone has an answer.

Someone update the description in my ticket, this meant that my images, write up has been lost.

I can view the History and see the text as (example)

*Create new page - Import Property List * Add permission Properties.Import/#Action * This will work in a similar fashion to the Property Components Prep Tool ** Allow user to ‘Import a list’ - this should work like on the Bulk Update page (e.g. Open a file, support file drop) ** !image-20240627-232759.png|width=405,height=62,alt="image-20240627-232759.png"! **

Now - there is 

• No way to CREATE a ticket from the History as far as I can see
• No way to COPY the Markdown and then Create a new ticket and PASTE that into the Description field and have it interpret it

Either I am missing something - or Atlassian is seriously causing issues for a laugh - why show me the history in Markdown if I can't use that Markdown back in the same product?!?

Anyone else been able to work through this?

[Matthew Lampey]

I have asked the very same question.  With some massaging, you can use the direct Create url, and it does let you enter markdown, but you can not see how it will render until the issue is created. 

• e.g. https://your-instance.atlassian.net/secure/CreateIssue.jspa

Can you copy and paste from the history... Nope.  And since on Jira Cloud you can not customize squat, I created my own markdown template for opening bugs.  Like code levels (14 different ones for me), device names, ancillary / attached devices, network info, specific configuration data.

But, when someone edits the template 'After' creation, in updates the history with like 5-7 pages of markdown that is not close to being readable.  

So, two thumbs up from me, and hopefully they will fix this someday.  Doubtful, but hopeful.