We have been using parent auto-transitions on Stories for the past year or so, but recently it stopped working. I've tried re-configuring it, doing the automation a different way (Execute Parent Transition vs Parent Issue Status), everything I can think of, and still can't get the transition to work. I really appreciate you taking a look as it's driving me insane!
I'm using the Validation on Subtasks Validator on the Story transition when the it goes from In Progress to Deployed QA. The validation says all App, Development, & DB subtasks must be in either Awaiting Prod Deploy, Closed, or Deployed status in order for the Story to transition. Please see attached screenshot of this validator setup. I did have a 'hide transition from user' condition on the transition, but it still didn't work even after I removed that condition.
Then the App, Development, & DB subtask workflows have the "Copy a parsed text to a field" post-function on the transition going from Ready to Deploy to Awaiting Prod Deploy (which is the status required in the above validator), to update the parent issue status to Deployed QA (or to execute Begin Testing transition when using the execute option). Please see attached screenshot of this post function.
I also tried using the 'validation on subtasks' validator with the 'transition parent issue' post-function from JMWE, just to see if that combination worked, but no luck.
We are on version 6.4.8 of JIRA, which we just upgraded to in December from 6.2.8. We don't know when this automation stopped working, but it's possible it could have stopped working after the JIRA upgrade.
Thanks for your help, & let me know if there's other info I can provide.
-Keri Butler Salesforce Marketing Cloud