Heres the gist. We have a custom field for stories/sub-tasks called "migration blocker" (yes, no). We also have a dashboard showing all Stories, required for migration by sprint.
We're running into issues where a story will have 5 subtasks on it. 4 of which are required for migration, one is not. So I'd like to automate that when the 4 marked ("required for Migration" = yes) are done, the custom field on the Parent story changes "required for migration" to no, thus taking it off my dashboard.
From the start the story needs to show it's required for migration, as 4 of the 5 subtasks are, but once that's completed we no longer need to track it towards this specific deadline.
I made this automation, but I don't think it will work after looking at it because I need ALL subtasks marked 'Yes' to be done as well as if there are say, only 2 subtasks but neither are required for migration to automatically changes the story's custom field to "no".
Hi @Casey_Jones -- Welcome to the Atlassian Community!
If I understand you correctly, the workflow of your use case is:
Is this what you are describing?
I wonder about your edge case of 2 sub-tasks that were never set to migration "yes". Why would the parent's migration be "yes" for those?
Hi Casey - Welcome to the Atlassian Community!
I think I would probably trigger it off of any sub-task that moves to Done that has a value of Yes for the Migration Blocker.
Then take a look at the first use case in this article to see how to check on the parent and update it:
Take a swing and that and post back what you come up with. :-)
If I've understood your need correctly:
If so, this is how I did it:
^ The Condition checks each time a sub-task is moved to Done to see if there are any other issues which aren't in Done which still require migration. Using "None match" ensures absolutes against the 4/5 - as opposed to "some" or "all".
Let us know if this works for you!
Would this work if the 5th subtask (the one not required for migration) is not done?
Shouldn't I add after the trigger, If issue type equals sub-task?
otherwise wouldn't it run if the story is done?
My dashboard is set up for all stories != done as at a higher level we're only tracking current WIP.
Yes it would still work regardless if the other sub-task is open or closed.
The branch "Parent" is based on sub-tasks - so it assumes the trigger issue was one. There is a separate branch option for Epic - "Epic (Parent)"
This means closing the story would not trigger an action, even though the trigger requirement is met and it might show up in the audit.
To make it a little cleaner, you could add in the additional condition - so the rule would be:
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
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