Automation for custom field ignoring move from Backlog into To Do

Bud Herz July 6, 2021

Scenario - 
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.

Challenge - 
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?

3 answers

1 accepted

0 votes
Answer accepted
John
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 8, 2021

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:

Screen Shot 2021-07-09 at 8.50.55 am.png

Let me know if that helps!

Thanks,

John

0 votes
Bud Herz July 12, 2021

We appreciate the effort to help on this one, but a coworker has figured it out. Thank you to Trudy and John on this. John was correct and his suggest is in line with the solution we found. We basically needed to set them in order. 

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 6, 2021

Hello @Bud Herz 

Just to double check, are you working with a Company Managed or a Team Managed project?

Can you show us the details of the Automations in question?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events