Hello,
my goal was to move the tickets from a project (service portal) to the scrum board of the main project. To do it, I have created a jira automation: cloning the ticket to the main project and deleting it from the original one. But there is a problem: attachments are missing. How can I solve this? Or, Is there an other way to move automatically a ticket from a project to another?
P.s. I don't have the Administer Jira Global permission
Thanks!
Edit: I started to loose the description as well. And in some tickets it is now missing. Any ideas
Hello all,
if i'm reading all this correctly, then it's not possible to copy an attachment from one ticket to another while using automation.
but if that's the case
Why can we select the attachment field for copy in the automation rules ?
It appears that work is in progress for automation, according to this item in the backlog. The description and history indicate copying attachments for Clone was implemented last month, although I have not tried this yet.
https://codebarrel.atlassian.net/browse/AUT-1030
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Bill,
i'm having trouble understanding because suddenly it's working fine. I did the same as before and the attachments are being successfully copied.
Thanks for taking the time to answer me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That makes sense; as I noted it appears Atlassian is in the process of implementing that feature I noted above.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Francesco La Bianca -- Welcome to the Atlassian Community!
It is not possible to clone attachments with an automation rule using the built-in features. There is a suggestion to add this feature: https://jira.atlassian.com/browse/JIRAAUTOSERVER-150
You also note a problem copying the description. Would you please post images of your complete automation rule and the audit log details showing an execution of the rule? That may provide context for the community to offer suggestions. Thanks!
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok thank you very much. Is there another way to automatically move (or creating a ticket-link for) the tickets? e.g. using labels?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you're open to work with an app, you can try Deep Clone for Jira.
You can read more about this topic here: https://community.atlassian.com/t5/Jira-questions/Automation-for-Jira-Cloud-clone-issues-and-copy-attachments/qaq-p/1463414
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the images of your rule and audit log. I do not see anything that would clear the description, or prevent its copying. This symptom could be a timing problem where the source issue is deleted before the clone completes; you could test that by adding a Re-fetch action after the Clone and before the Delete to slow down the rule.
I recommend working with your site admin to submit a defect to Atlassian Support so they can take a look: https://support.atlassian.com/contact/#/
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.