nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Rafael Freymueller

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

Accepted answers

Kalyan Sattaluri_iinm1n

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.

All comments

Kalyan Sattaluri_iinm1n

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

Deleted this comment and added as reply to other comment

Rafael Freymueller

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_iinm1n

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.

Rafael Freymueller

Thanks again for the massive help!

I will try this out tomorrow and report back with the results.

John Funk

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation