Images missing for cloned issues

[Danilo Resende]

Hello, the images on Issue description are missing when I clone a Jira Issue, check the screenshots below. Am I missing something? Or is this a bug?

Original issue

Cloned Issue:

[Angélica Luz · Accepted solution]

Hi Danilo,

Thank you for reporting this issue to us, I was able to replicate the same behaviour on my test instance and validated that it only happens when using the new issue view.
Based on that, I created a bug for our dev team to check:
- https://jira.atlassian.com/browse/JRACLOUD-71950
Please, click on vote and watch to receive updates.

Regards,
Angélica

[Ben_Chamberlain]

I'm experiencing a similar issue. This may technically be a feature request but feels like a bug.

I have JIRA automation to set up a clone of a JIRA from our discovery board to our development board under a condition.

Attached images do not load. Retry does not load them. Looking at the documentation, it seems cloned issues are not expected to have working attachments/images. For my workflow, not having images on clones takes away the value of cloning.

[Deleted user]

Same experience as both of these above cases.

[Bikash Agarwal]

It is very annoying. Beside, also when exporting to the word, it still does not load the images, rather provides the link. Annoying.

[Deleted user]

Hello Angélica,

Is there an expected resolution time for this issue?

[Angélica Luz]

Hello @[deleted],

Welcome to Community!

We still don't know when it will be fixed. I see that you added a comment asking for an update on the bug and also, someone from Atlassian added an internal comment asking for an update. 

Checking internally, I see that they are already talking about rolling out a fix for this bug, so let's wait for a few days to check if they will add an update on the bug ticket.

If they don't, I'll ask them again next week.

Regards,
Angélica

[Deleted user]

The issue is not yet fixed and is really annoying. It has been open for 5 months. Kindly expedite the bug fix.

[Angélica Luz]

I sent a message to our devs again and they said that it's a long term backlog. They will fix but it's planned for farther in the future.

The workaround, for now, is to go to the old view and append some text on the description and then go back to the new view. The steps are mentioned in this comment.

[Paul]

...

[Kit Teguh]

Any updates for this issue? When my cloned ticket is created, I need to manually reattach the images from the original ticket, which is time consuming and just add more unnecessary work. Can the Atlassian team address this issue sooner rather than later instead of taking literally years to even consider fixing the issue?

[Ingram Canterbury]

This is clearly a big issue and it seems to be split amongst several tickets, none of which are "truly" resolved. This is a significant limitation for my team.

[Gabi DAbato]

Do we have an update on the cloning issue? Its been over 4 years and it still does not work as it should. 

[Amanda Coughlin]

You just have to include attachments. The attachments are what copy the images over. 

[Amanda Coughlin]

If you create an automation rule you can select the fields to copy description and attachment and that worked for me. 

[Jonathan Cooke]

I don't understand how this is so low on the priority list. The clone function is effectively broken and I have to manually re-copy the contents from the original ticket every time I have images (which is most of the time). The work around in the ticket does not work.