Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Automation: After cloning an issue, the linked issues do not show which was the original issue that

Cláudia Silva May 22, 2024

Hello,

I created an automation in which after a JQL condition I am cloning several types of issues, the task itself and its sub-tasks.
The problem is that after cloning the task itself, when I open it, the type "clones" does not appear in the "Linked issues".
But in the sub-tasks it appears normally. What could be the problem?

Clone issue.png
Thank you !!

1 answer

0 votes
Gikku
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 25, 2024

@Cláudia Silva I was able to reproduce the issue that you have mentioned here and I would assume it is the default behaviour of the automation rule. You can add an additional step as in the below screenshot to set up the 'clone' link between the new and existing issue as a workaround. 

Screenshot 2024-05-25 at 10.36.18 AM.png

Cláudia Silva May 27, 2024

Hi @Gikku , thank you so much for your answer.


I already tried that way but I wasn't successful either, the alternative I came up with and which solved the problem was to add an issue link of the "Cloners" type in the additional fields, just like the screenshot and thus adding the link to the original issue. ..

Cloners.png

Like Gikku likes this
Gikku
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 28, 2024

@Cláudia Silva I am not sure why it failed for your rule, but I tested mine and seems to be working perfectly.

comm.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
TAGS
AUG Leaders

Atlassian Community Events