Is it possible to create an automation rule with conditions based on issues found in LookupIssues?

[Anastasiya Lebedev]

Hi, I'm trying to figure out if the following is possible:

I want to schedule a daily Slack message that will include a digest of issues that changed status today.  If any of these messages have specific labels, I want to tag specific Slack users.

I.e., 10 issues progressed to done, 1 had the label "Purchases" (relevant for Bob), 2 had the label "Marketing" (relevant for Alice), none had the label "Books" (relevant for Sylvia).  Therefore, I want to post the list of the issues to Slack (this works), followed or preceded by messages that will tag Bob and Alice, but not Sylvia, all of this executed in one rule.   Is this possible?

Thanks in advance for any help!

[John Funk · Accepted solution]

Hi Anastasiya - Welcome to the Atlassian Community!

I have not tried this but it might be possible to do the Slack post with multiple issues using the lookupIssues function. and then add a Branch after that based on JQL that would then send separate messages. 

Again, I haven't done that, but that's the path I would go down to try it. 

[Anastasiya Lebedev]

Hi John,

Thank you for your answer!  I guess what I'm having difficulty with is, the branch conditions seem to refer more to trigger issues, which wouldn't be the case for a scheduled rule with lookupIssues.  So trying to figure out how I would do that and whether it's possible.

[Anastasiya Lebedev]

Spent too much time today trying to base additional issues on labels, eventually had to just make a new JQL request for each label, because there seems to be no way to parse the labels from lookupIssues using smart values functions.

[John Funk]

Why don't you just use the same JQL in the Branch that you use in the Scheduled trigger? 

[Anastasiya Lebedev]

I can't find a way to evaluate the labels of the issues, they don't seem to be accessible.  I need to compare list A (the labels of the issues retrieved by JQL) with list B (my list of labels that are relevant to particular users), and I can't access this list A in any way.

[John Funk]

Is this labels field a custom field that you created in a Next-gen project? How many different labels fields are you using? 

[Anastasiya Lebedev]

Nope, standard Jira issue labels in classic projects. 

[John Funk]

The labels field is a universally available field with the same values showing for every project. So I am confused now as to the question as there are not separate values in the labels field that are associated with certain users. 

Can you provide more details? 

[Anastasiya Lebedev]

The association is not in Jira, it must be made with the help of automation.  (IF any labels in the issues retrieved with lookupIssue have label "Marketing", ping Alice on Slack when outputting the list of issues).  However, I have not been successful in accessing the labels field of issues in lookupIssue.

[John Funk]

Sorry, I understand better now. No, the labels field is not available using the lookupIssue function. See the document for the list of available fields under the section on lookupIssue:

https://support.atlassian.com/jira-software-cloud/docs/automation-actions/

[Anastasiya Lebedev]

Thank you :) most importantly, I figured out how to get what I want, even if it's more or less brute force.

[John Funk]

Hi @Anastasiya Lebedev  - If this took care of your question - can you click the Accept Answer button to close this one out? Thanks!