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; } } }

Jira issues that are clones: the automation will not work

Chris Covert_h0jutu

Hi,

We have an automation which is basically:

when a story/bug transitions from To Do Status to Analysis Status : create 6 new sub-tasks.

it works great.

However:

If you take a JIRA issue and clone it, and then go into the clone and transition it to analysis status, the automation does not run.

We have looked very closely at this and can't figure why it is not working.

Thanks

Accepted answers

All comments

Trudy P Claspill

Hello @Chris Covert

Can you please share with us the automation rule you created?

Are you sure the rule is not running, or is the rule running but encountering a condition that does not pass? Check the Audit Log to determine if the rule is running for the clone issue. You can also click on the Rule Executions field in the Details panel of the individual issue. That will pop open a panel that shows you a history of the rules that have executed against that issue.

John Funk

Hi Chris,

Is you are trying to run the rule on the Clone, then that's a Sub-task issue type from what you have said so far. And that doesn't appear to be covered in the condition for which issue types you are running the rule for. It will all depend on how your Conditions are setup.

If you will post your rule here we can give you better feedback.

Chris Covert_h0jutu

Solved!

Thank you, I had looked at the audit log before but then took a deeper dive into it, realized it is more powerful than I first thought, and it lead me to the solution.

Thank You!

Chris

Chris Covert_h0jutu

Wait, I never tested it, it still seems to have an issue.

The cloned task has a label that exists that is created by the automation. If the label does not exist the automation can run. I removed the label and try to run the automation but it does not run. The audit log says it failed because the label exists, but the label is not there.

Chris Covert_h0jutu

2nd snippet: has the label that if exists will not let the sub-tasks be created. But 3rd picture shows the issue we are trying to run execution of automation: the label field is empty.

Will keep double checking this.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud