Automation - Compiling unfinished subtask owners in a string

[Tom]

We work in a multi-team environment with lots of interdependencies.   I'd like to have a field on a story/bug that has an up-to-date list of everyone who has a subtask remaining on the main story/bug ticket.

Example

• Story PROJ-1011
  • Subtask PROJ-1022 assigned to Bob which is in "DONE" Status
  • Subtask PROJ-1027 assigned to Tim which is in "DONE" Status
  • Subtask PROJ-1035 assigned to Bob which is in "IN PROGRESS" Status
  • Subtask PROJ-1037 assigned to Bob which is in "TO DO" status

  • Subtask PROJ-1022 assigned to Sue which is in "TO DO" Status

Assuming we had the field "Notes" on the Story, I'd like the Notes string to be "Bob, Sue"

This excludes:

• DONE status items
• Dedupes Bob from appearing twice. (this part is optional, if we can get everything else working and have some duplication that's still a victory)

The trigger events are anytime a subtask class issue is created, updated or assigned, to cause a rebuild of the list on the parent story/bug.

I've had success with getting the string built with a branch to the parent and then a field update action with:

      {{issue.subtasks.assignee.emailAddress.substringBefore("@").join(", ")}}

But I've had no success after many tries at not including the Done items or deduping.  Any help or pointers would be appreciated.

Current setup:

• Trigger: Multi-trigger on create/assigned/closed
• Condition: Subtask class issue
• Branch: Parent
• Lookup issues: issueFunction in subtasksOf("key={{issue.key}}") AND NOT Status = Done
• Edit field: {{issue.subtasks.assignee.emailAddress.substringBefore("@").join(", ")}}

[Bill Sheboy · Accepted solution]

Hi @Tom 

Removing the duplicates may be done using the distinct list function:

https://confluence.atlassian.com/automation/jira-smart-values-lists-993924868.html#Jirasmartvalueslists-list.distinctlist.distinct

Your current rule is triggered on a change to a Subtask, and so the lookup issues action should only return Subtasks which are siblings to the trigger issue, and not Done.

Once you have made that adjustment, please add the distinct before you join(", ") the values together.

Kind regards,
Bill

[Tom]

@Bill Sheboy 

Thanks for that fast reply. Holiday weekend over and I'm back to it this afternoon.

!!The distinct worked like a charm, thank you for that!

The part to eliminate the Done subtasks from the compiled string isn't quite making sese to me.  Sorry for being dense.

When you say "Your current rule is triggered on a change to a Subtask, and so the lookup issues action should only return Subtasks which are siblings to the trigger issue, and not Done."

My lookup is "issueFunction in subtasksOf("key={{issue.key}}") AND NOT Status = Done"  

I'm just not understanding what you suggest changing as this is not working for me and still results in a string with the names from all subtasks including the done ones.

Edit to add:

I've tried that query several different ways and while in Jira search it returns the correct set of subtasks, when used in automation, any filtering seems ignored other than the subtasksOf().  Put in filters by subtask type, status, etc.  Put them before and after the subtasksOf().  Every time, everything but the subtasksOf() is ignored.  Weird stuff.

Edit again: 
Converted it to use JQL branching instead of parent branching using:
"project = ZZZ AND issuefunction in subtasksOf( "issuefunction in parentsOf('key={{issue.key}}')") AND NOT issuetype = "QA Test" AND NOT status = "done""

And it still ignores everything but the two issuefunction commands

[Bill Sheboy]

That JQL function is from an addon / app, and thus I do not know if it works inside of automation rules for Jira Data Center.

As an alternative, you may use built-in JQL features.  Assuming the trigger issue is a subtask, that would be this to find the sibling subtasks with the same parent for the lookup:

parent = {{triggerIssue.parent.key}} AND status != Done

And then getting the list you describe would be:

{{lookupIssues.assignee.emailAddress.substringBefore("@").distinct.join(", ")}}

[Tom]

@Bill Sheboy 

First, thank you for your persistence and patience and willingness to help with this!  

That is exactly the issue.  Thank you.

The original edit action referenced:
   {{issue.subtasks.assignee.emailAddress.substringBefore("@").distinct.join(", ")}}

Which would iterate through al subtasks regardless of any filtering in the Lookup action.

Changing to:

  {{lookupIssues.assignee.emailAddress.substringBefore("@").distinct.join(", ")}}

Corrected my foundation issue by referencing the lookup results instead of the full set of subtasks.  

Your help is greatly appreciated in helping me learn and understand this.  Thank you.!