-
Bug
-
Resolution: Timed out
-
Low
-
1
-
Minor
-
Issue Summary
The old issue view lets you add an inline image in wiki markup to a non-existent attachment. The attachment will be displayed correctly if it is uploaded later. In the new issue view the attachment will not display correctly.
Steps to Reproduce
- Add an inline image in the Description field of an issue on the old issue view, using wiki markup such as
!image.png!
Make sure the image file is not currently attached to the issue. The description will be rendered as "Unable to render embedded object: File (image.png) not found".
- Attach the missing image file to the issue and refresh the old issue view. The inline image should be displayed correctly.
- Switch to the new issue view. The attachment will not display correctly:
This is a problem because when you create an issue using the REST API, you cannot pass attachments to the POST /rest/api/2/issue endpoint, so you first pass the Description as a wiki-markup string, and only after can you add the related attachments. Which means inline attachments will show just fine on the newly created issue under the old issue view, but not under the new issue view.
Same thing of course if you set the Description field using the PUT API. You'd need to first make sure to copy all the required attachments, which is not intuitive.
Expected Results
The attachment displays in the new issue view after the file is uploaded
Actual Results
The attachment fails to display.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Jira Cloud team