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
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I just realized it is not a labels
It is looking for a rules execution in the cloned items that equals TeamTasks as per snippet 2 (middle) I was reading too quickly.
How do you delete the Rules Execution Swat tasks from an issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I figured it out:
Someone created a new labels based custom field called RulesExecutions
I made it visible on all issues and now people just make sure cloned issues have the label deleted before running the automation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.