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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.