We use a dev board that clones a 'Done' ticket into the 'To Do' of a QA board. Extensive automation using the 'If/Else' method covers everything we need for a custom field to change during transitions across the board. Once a ticket is in the board, moving around between To Do/In Progress/Done executes all automations as expected.
Creating any issue with the global top nav 'Create' button then choosing to add it to the QA board sprint does trigger this automation just fine. The field populates as the automation is set up.
Trigger for the custom field is Issue Created. Upon creation of the clone though it's placed in the Backlog. The automation ignores the ticket here. It does not execute the process.
If we move the cloned issue from the Backlog into to the current sprint (in the 'To Do' column), it is still ignored because it wasn't created(?) there.
Challenge (extra layer) -
Although by that point there is a second automation that should recognize the ticket is "To Do", has an empty field, and should change the field in question. This also fails.
Current solution -
For now we're dragging it in and out of the To Do column for the automation to act on the issue. This is less than ideal of course at the rate we're trying to work.
Why is a cloned issue not viewed as a created issue for this automation?
Hey @Bud Herz
Am I correct in saying you have an automation running that clones this issue and you want this automation to kick off a separate automation?
If that is the case please make sure you allow the rule to be triggered by another automation. You'll find this on the rule details page:
Let me know if that helps!
Hello Community! We thoroughly enjoyed this just-for-fun conversation in the Jira Admin Group about what it's like to be a Jira Admin. For #JiraJuly, our talented designers created these graphics t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events