The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to restore inline images in description field in jira

Jiragodarigunta
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 27, 2025

During the jira migration using bulk edit option, some of the ticket descriptions were unintentionally overwritten, when i checked the ticket history and copy pasted the description inline images are not rendering. 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Vitalii Rybka
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 Champions.
June 27, 2025

Hey Jiragodarigunta,

That's a frustrating situation  inline images getting lost during bulk edits is unfortunately pretty common. The issue is that when you copy/paste from history, you're only getting the text references to the images, not the actual image attachments.

What's happening: Jira stores inline images as attachments with special references in the description. When the description gets overwritten, those references break even if the attachment files still exist.

Try this:

  1. Check if attachments still exist look at the ticket's attachment section
  2. Re-upload and re-embed -if the image files are still there, download them and re-add them inline
  3. Use REST API if you have many tickets, you might need to script the restoration using Jira's REST API to properly link existing attachments back to descriptions

Prevention for next time:

  • Always backup before bulk operations
  • Use Jira's native export/import rather than bulk edit for complex content
  • Test bulk operations on a small subset first

Last resort: If you have a recent backup or can access the data from your migration source, that might be your best bet for restoring the images properly.

This is definitely a pain point with Jira's bulk operations. Hit me up if you need help with the API approach or want to troubleshoot further!

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events