Automation: Duplicate Issues with a certain component on a monthly basis

Rafael Freymueller May 2, 2024

Hi,

I'm fairly new when it comes to working with Jira Automation so please bear with me! 

The automation I am trying to setup is to clone all issues with a certain component on a monthly basis. When I try to run the rule I get the following error messsage: 

"Branch rule / related issues. Can't branch rule as it requires issue(s) in the context for this option. More than likely you have a trigger that doesn't insert issues into the rule chain. e.g. Scheduled rule not running a JQL query. Creating an issue does not put an issue into the context, you have to branch on it directly."

I would highly appreciate if someone could explain to me what I am doing wrong and how I can find a suitable solution. 

Thanks in advance! :)

 

Test Automation.PNG

3 answers

1 accepted

1 vote
Answer accepted
Kalyan Sattaluri
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 2, 2024

Hello @Rafael Freymueller 

In your Scheduled Trigger section, further below, there will be a checkbox to provide JQL.

select that checkbox, and provide JQL for issues you are interested in.

Maybe something like==> issuetype = Story and status not in (Done, Cancelled) and components = test

^update based on your criteria

That starts your rule with a list of issues, and if you want to clone them, you dont need to branch. You directly call "Clone" and give your details. 

Rafael Freymueller May 2, 2024

Thank you Kalyan for the quick and helpful reply!

Would it also be possible to set a component or label for the cloned tickets based on the current month that we are in?

For example, if the tickets are cloned on the 1st of May, the component should automatically be set to "May". From my understanding this would be quiet tricky with the date format and the necessary conversion in Jira.

I marked my initial question as Done as you have answered it!

Kalyan Sattaluri
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 2, 2024

Hello, Great to hear..

For the issue getting cloned, if you want to assign it a component which is equal to the current month, you can use {{now.format("MMM")}} smart value like I have in my screenshot. This will assign "May" if I am cloning it today..

NOTE - You need to create all these components in the project ahead of time.. else it will not assign, obviously. Hope it helps.

 

image.png

Rafael Freymueller May 2, 2024

Thanks again for the massive help!
 
I will try this out tomorrow and report back with the results.

 

Like Kalyan Sattaluri likes this
Rafael Freymueller May 3, 2024

Hi Kalyan,

one more question that came up is how do I transition only the cloned issues to another column?

Right now I have the automation in place that you recommended yesterday.

Best regards,

Rafael

0 votes
John Funk
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 5, 2024

Hi Rafael,

I don't know your exact scenario, but take a look at this article to see if it would also help you solve the need. It clones the issue automatically when it is closed/marked Done based on whatever timeframe you have identified. 

https://community.atlassian.com/t5/Jira-articles/Creating-a-Flexible-Recurring-Task-Issue/ba-p/2040862

0 votes
Rafael Freymueller May 2, 2024

Deleted this comment and added as reply to other comment

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events