Hi,
I have a project where we capture issues from a portal in project 1, and then they get created and cloned into this project 2. Everything works fine, but now I want to implement the following:
- Issues cloned into Project 2 need to move from NEW to LEAD TECHNICIAN, which should be pretty easy but it doesn't even acknowledge the issues and nothing in the logs.
- This rule works for issues created from an API into Project 2, it immediately transitions those successfully.
Rule below for details.
I have been breaking my head trying to figure out why it only works with issues created through an API, and not with these issues created by an automation.
If anyone can give me some idea what is going on here.
Thank you,
How are the issues getting cloned into Project 2? Is that being done by a user or through another Automation Rule?
<Edited to correct TYPO in answer!>
If cloning is done through another Automation Rule, then check the Rule Details on the rule you created to transition the issues. Make sure this box is unchecked checked.
Yes, it is being cloned by an automation rule from Project 1 into Project 2.
I checked the rule in Project 1 and that box is already unchecked.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You said "I checked the rule in Project 1 "
You need to check the rule in Project 2 - the rule you showed us that is trying to transition the issue to a new status.
Is the Transition rule being triggered at all when the Clone rule creates the issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Apologies. Correction I checked Rule for Project 2. Here is a screenshot and this rule works when tickets are created through a service account from other environment (Bitbucket) but not when they are cloned from Project 1 to Project 2.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
And my apologies to you. I have a typo in my original reply.
The rule in Project 2 needs to have that box checked so that the rule in Project 2 can be triggered by actions that occur from other rules having executed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You're welcome. Sorry for causing any confusion with the typo in my original answer.
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.