441e7ea28a31 could you support ** Lê Nguyễn here please? (See the latest comment)

owallis@atlassian.com  now we encountered a similar bug on Jira platform cloud

Great! Yes, it's working!

Hi f5c9ee1983b3 (and the other people watching this ticket)

We've done testing internally. We think the feature is working (although a bit hidden)

When setting an automation rule click the button "Choose fields to set..." and select attachment

You should then see the option above. And on running the rule attachments would be cloned.

Could you try this and let me know how you get on?

Having the same issue Any update on the resolution?

I want to report this issue as well.

every clone or automated tickets doesn't include images

When this will be solved ??

Our organization would like to report as well that this issue is not yet fixed - we are currently having this problem with automatically cloning issues with the images in the description field. Manual cloning works alright once the "Copy attachments" checkbox is checked, but when cloning automatically the problems still persist and should be reinvestigated.

Hi folks, I'm the PM in Media

Looking at the comments this issue does not appear to be fixed.

It also appears this ticket is a duplicate, with https://jira.atlassian.com/browse/JSWCLOUD-22482 being the source of truth I'll use from now on. Please watch/vote on that ticket (although I will check for comments here periodically).

This affects our workflow as well. Broken when cloning via automation

Hey we have this issue as well. Using HALP > auto create bug issuetype in Support Board > close issue as DELEGATED > Clone to selected team board via custom field = No image preview in description

Affects my team. Still broken with Automation flow.

I'm having this issue too, when I cloned the issue via Automation. The images on the description are not copied across.

Hi all,

Just confirming that images/attachments are not yet supported when cloning issues via an Automation rule - there's an open ticket for this here: https://codebarrel.atlassian.net/browse/AUT-1030

Cheers,

Charlie

This issue is affecting my team, too. We are facing it on issue cloned by Automation.

This issue is affecting my team, too. We are facing it on issue cloned by Automation.

Commented on wrong ticket.

This is still an issue for us as well. 

still experiencing this - have linked  issues that do not appear on the cloned issue

Still broken, can this be reopened

Definitely not fixed in cloud, using automation to clone issues and both descriptions as well as comments have images as failed to load.

Also facing this issue when cloning stories across projects using automation.

Also happening for us using Jira Automation to copy description data across to a new ticket in a separate board.

Seeing the same issue on my instance, cloned an issue manually (not through an automation rule) and the new 'cloned' issue has the failed error.

I've just setup an automation rule to clone a ticket from service desk project to a software project and get this error as well, don't see this as fixed. 

45e190d61f2e please request help from our Support team at getsupport.atlassian.com. The use case you are describing (cloning from one project to another) does not appear to be a standard process. To get the best help for your situation we need to see what's happening in your case.

237939bc7083 I will be creating a new issue specific to Automation Rules that you can track. EDIT: there is an existing issue that covers this problem: JRACLOUD-74937

Manual cloning also fails, when cloning from one project to another. I still get the message "Fails to load" on top of image icons. Please reopen the bug and work on it.

@Michael Tokar

Manually cloning an issue and ticking off "Clone Attachments" works:

However, as  alejandrosejas says, doing the same task from Automation

link titlecreates errors. Specifically, I have a rule cloning an Incident into a Change Request, and when the clone has been created, the attachment icons are visible, but not accessible, the just show with the text "Failed to load" and "Retry":

It seems that the Automatoin functionality  fails to create an attachment in the same way as in the "manual mode", which should not be the most challenging code to implement in the Automation, either as a default "always clone attachments" or by a ticker "Clone attachments" as in the manual step

And talking about attachments.................. seems like mine would not be applied here either

a46772c82a0b does the problem exist if you manually clone issues (i.e. not through an Automation Rule)?

The issue still persists. Just created an automation rule to Clone Stories, and their attachments (in the cloned story) have the message "Failed to load"

Thank you!

This issue has been resolved. You should now be able to clone issues with attachments and have the images load. See the screencap for a demo.

Thanks,
Jira Cloud team

Resolved issue is not accessible. I'd like to have access to the information about BENTO-5142 or someone from Jira could share information here since it is listed as "is resolved by".

This makes no sense to me. Why is this even a bug that we need to watch and comment on? This functionality has been working fine for months, Jira made an update, didn't properly QA their product and now paying customers are having to spend time watching, commenting and asking Jira to fix what shouldn't have been broken in the first place. Lost time, lost productivity, exceptionally frustrating. Please just fix it!!!

Do you have an expected resolution time for this issue?

please fix as having the ability to view the full detail of the issue and image provides help to resolve the issue in a timely manner. 

This is a big one for us. It's really hard for our team to work efficiently when this isn't functioning properly. It's a big pain point.

Please fix this as it is a major frustration for us at this point.

please please fix  this is a huge pain and we've tried 100 work arounds. 

+1 we use copy function between service desk and backlogs for teams. Without images it both slows the fixing process as well as causes permission issues as we need to have multiple authorizations for both systems.

Would like to see this escalated

I see the priority on this is low.  It should be high as not being able to clone attachments or images that are in  a description makes the Create Issue and Clone automation virtually useless.  When will this be fixed?

Hi,
I have the same problem in the cloud jira when making a clone that contains image or attachment via automation.

This has happened to us in the last 2 weeks, and is very annoying. 

This still happens to me, and it's super annoying.

I clone tickets a lot and I would appreciate having this prioritized

We just ran into this issue today on Cloud when cloning the issue. The attachments come over, but the the description's preview is still showing failed to load.

Still happening for us, with issues cloned within the last 24 hours. 

We desperately need this fixed

We still have this issue it it's necessary to do something for this update/fix?

We still face this issue as well..

EDIT: My bad, there has been a fix on Jira cloud over the weekend. it is working now as intended

Still an issue.  Doesn't pop up often, but when it does can take hours to re-re-re-re-upload images (when splitting a large story into several smaller ones). 

Don't see how this isn't a quick fix from the Jira team.

I would love to see this fixed, is a hassle that leads to additional copy / pasting of images (which Jira often then rejects due to https://community.atlassian.com/t5/Jira-questions/Unable-to-save-a-jira-ticket-because-of-formatting-issue/qaq-p/1062513?utm_source=atlcomm)

Same for us, this is a real pain. Please fix.

I second this. This is a real pain, and has me evaluating additional plugins (which probably aren't the right solution...)