How can I filter issue type by smart value?

[Casper]

This part of automation sends a comment when all Sub-Tasks are in status 'In Progress'
And notify everyone who is assigned to any sub-issue type of Parent Task:

The same case here, but automation sends when all Sub-Bugs are in status 'In Progress'

Also tags everyone who is assigned to any sub-issue type of Parent Task:

Here are all my sub-issues of Parent Task, Here you can see two Sub-issue Types:

- Sub-Task ( On top of the screen )

- Sub-Bug ( On bottom of the screen )

Below is how automation sends the comment in two cases:

- All sub-tasks are 'In Progress'

- All sub-bugs are 'In Progress'

As you can see automation tags everyone who has been assigned to some sub-issue of the parent task.

What do I need? 

- In case when all sub-tasks are in status 'In Progress'
I want to receive the same comment but with peoples who are assigned to all Sub-Task only, not from sub-bugs too.
( I mean do not recieve from all sub-issues of the parent task, only from sub-task )

- The same with second case, when all sub-bugs are In Progress,
I want to recieve a comment with everyone who are assigned to Sub-bugs only.

So how can I handdle ths case with Jira Smart Values or maybe some another solution.

[Bill Sheboy · Accepted solution]

Hi @Casper 

I believe you would need to do this in two steps, for each issue type involved: filter by type and then use distinct:

• inside one of your conditions on type for the trigger issue, create a variable which filters by type and only save the assignees' accountId
  • name: varAssigneesForSubTasks
  • smart value:
    • {{#issue.subtasks}}{{#if(equals(issuetype.name,"Sub-Task"))}}{{assignee.accountId}}{{^last}},{{/}}{{/}}{{/}}
  • Please adjust the issue type name(s) to match your configuration
• now to send the mentions, split the created variable back into a list, and use distinct on it
  • {{varAssigneesForSubTasks.split(",").distinct}}

Kind regards,
Bill

[Casper]

@Bill Sheboy

Thank you a lot!

Did I do it well?

Because i not sure i place variable in the right place.

All the best,
Ostap

[Casper]

Also, I tried this case, and it doesn't work.

I'm sure I missed something.

[Bill Sheboy]

Yes, the created variable needs to be inside the condition (and branch) to do this for each issue type case.

Sorry, I left off some details on doing the mentions...

This produces a list of accountId values:

{{varAssigneesForSubTasks.split(",").distinct}}

And that must still be parsed into mentions, like this:

{{#varAssigneesForSubTasks.split(",").distinct}}[~accountid:{{.}}]{{^last}}, {{/}}{{/}}

[Bill Sheboy]

Oops, my mistake!

The created variable expression was incorrect as I left off the assignee field!  I fixed the earlier post and here it is also:

{{#issue.subtasks}}{{#if(equals(issuetype.name,"Sub-Task"))}}{{assignee.accountId}}{{^last}},{{/}}{{/}}{{/}}

[Casper]

@Bill Sheboy I fix that, but it still doesn't work.

Here is what Jira comments send:

Also here are more details on how I use your solution: Link

[Bill Sheboy]

Would you please post images of:

• your current, complete rule
• the details of the create variable action(s)
• the details of your use of that variable in the mention

And...did you confirm the exact names of your sub-task types?  If the names are not correct the created variable results will be empty.

You can confirm that by adding a write to the audit log immediately after the trigger:

the issue type's name is: {{triggerIssue.issuetype.name}}

[Casper]

True,

name was Sub-task, not a Sub-Task.

Sorry, I though that the upper letter didn't effect the result.

Thank you a lot Bill for your effort.

All the best,

Ostap

[Bill Sheboy]

Just to confirm, is the rule working now?

A work-around for that challenge with capitalization is to force the text to lower (or upper) case before the comparison/filter.  Although that is not always what is desired for matches.

[Casper]

Yes it works!

[Casper]

Sorry for my mistakes @Bill Sheboy , my head starts a little bit exploding)

The solution:

The sub-tasks:

The result:

Did I miss something?