You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
My team is currently utilizing a project board alongside several other teams as an intake process for IS requests. Each department monitors said board and approves and routes their requests to their individual team project board (via automation rules).
In this transition automation, comments and attachments do not transfer from the original request to the new "cloned" request that is created within our individual projects. This forces us to go back and review the original, linked issue.
Is it possible to set up the automation to have the comments and attachments clone to the new issue once it is cloned to a different project board?
Below is a screenshot of what the automation currently looks like - since there are multiple projects that utilize this automation, the cloning of comments/attachments would need to transfer to every project. Is this possible?
Welcome to the community. Apparently there is an option to copy the attachments as explained here: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Clone-issue
To copy/clone to other projects, you will have set the automation in the global administration section which you will need a sys admin to do it.