Transition status of a Story when all sibling Tasks and Bugs are completed.

[Keir McGuffog]

We have a project set up with a number of epics, each consisting of a story and multiple tasks. We want to transition the status of the story from AWAITING DEV to READY FOR QA when all of the sibling tasks (or bugs) in the epic have a status of READY TO DEPLOY, DONE, or OBSOLETE (or a status category of Done). Thanks in advance for any help.

[Keir McGuffog]

Again, posted by mistake.

[Keir McGuffog]

Posted by mistake.

[Mark Segall]

Hi @Keir McGuffog 

So you're saying that each Epic will only have one story and a bunch of related Bugs/Tasks?  If so, you could do something like this:

• TRIGGER: Issue Transitioned (To Ready to deploy, Done, Obsolete)
• ACTION: Lookup Issues
  
  • issueType != Story AND "Epic Link" = {{issue.Epic Link}} AND status NOT IN ("Ready to Deploy", Done, Obsolete)
• CONDITION (Advanced)
  • {{lookupIssues.size}}
    Less Than
    1
• CONDITION: Status not equal to Ready for QA
• ACTION: Transition Issue (to READY FOR QA)

[Keir McGuffog]

Hi, and thanks for the response. I've tried the config above but have had it come back as failing. I'm guessing that this is due to the Story workflow being different to Tasks and Bugs?

To answer your question, yes, each Epic will have one story and a bunch of related Bugs and Tasks.

Here's the Task/Bug workflow...

...the Story workflow...

...and the audit log.

[Mark Segall]

It looks like you'll need to add a condition before the lookup issues action

Issue Type = Story

[Keir McGuffog]

No, I'm afraid it's still not behaving as hoped.

These are the issues I'm using to test...



...and this is the audit log.

[Mark Segall]

Sorry - Let me take this a step back because we may have gone off path a bit.

You want when all bugs/tasks transitioned to Obsolete, Ready To Deploy or Done that the Story should be transitioned to Ready for QA.  The rule needs to be tweaked (this is on me)

• TRIGGER: Issue Transitioned (Obsolete, Ready to Deploy, Done)
• CONDITION: Issue Type NOT EQUAL Story
• ACTION: Lookup Issues

  • issueType != Story AND "Epic Link" = {{issue.Epic Link}} AND status NOT IN ("Ready to Deploy", Done, Obsolete)

• CONDITION: Advanced
  • CONDITION (Advanced)
    • {{lookupIssues.size}}
      Less Than
      1
• BRANCH (JQL)

  • issueType = Story AND AND "Epic Link" = {{issue.Epic Link}} AND status != "Ready for QA"

  • ACTION: Transition Issue (to READY FOR QA)

[Keir McGuffog]

Yes, to confirm, when all bugs and tasks are transitioned to Obsolete, Ready to Deploy or Done, the Story within the parent Epic should be transitioned to Ready for QA. Unfortunately, those tweaks are still missing something.

Here's the audit log again...

NB I tweaked the BRANCH JQL rule as there seemed to be an extra AND, which was causing an error, and it makes sense for the story to only be transitioned if it originally has a status of "Awaiting dev".