Trying to create an automation that sends issues still in review for a specific Jira Board.
The challenge is that the Slack Message includes additional issues that are not included in the Lookup Issues.
For example, this SQL finds 4 issues for this CS board (see image). However, the Slack message in the channel shows 33 issues (includes issues in review rom other projects). Why are other projects included in the slack message?
Slack message field:
Currently there are {{lookupIssues.size}} tickets in review,
{{#lookupIssues}}
:white_medium_small_square: <{{url}} | {{project.name}} - {{key}} - {{assignee.displayName}} - {{summary}}>
{{/}}
One thing that pops out at me immediately is I believe your JQL may be flawed? As written that JQL will return issues outside of your CS project since you have the OR statement outside of any parentheses. Maybe your JQL should look like this?
project = CS and status in (“in review”, “in test”)
Thanks, Jack! The JQL seems to come back with 4 issues which is the number I expect.
It doesn't seem to like this JQL? Maybe because of the "in" word is part of the status
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The JQL looks right. By having those multi-word statuses in quotations should take care of the confusion it is complaining about.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Andrew Hickey , a couple of comments…
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Jack Brickey and @Curt Holley !
1. This is a project rule. I included the "project = CS" just in case it was helpful.
2. Excluded the "project = CS" but still receive the same error :/
3. Regardless, my previous JQL receives 4 issues found, but my slack message shows 33 issues.
4. If I remove the "Project = CS" from my initial JQL, then my slack message shows 47 tickets (despite this being a project rule)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Put the Project = CS back into your lookup issues action.
and
What is in your schedule? does it have any JQL configuration?
If not, then add your same JQL there. That way only those 4 issues are part of the rule from the get go.
Of course all of this does require getting your JQL to work. But totally agree with @Jack Brickey . Get it working in Advanced Search, copy into the rule....and it should be fine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you @Curt Holley and @Jack Brickey !
The advanced search helped a lot. Just copied into the rule like you suggested :)
for anyone experiencing a similar challenge, I updated my JQL as listed below after testing with the Advanced Search
(project in (10017)) AND (Project = CS AND status = "in review" or (status = "in test"))
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is an interesting JQL.
Why the (project in (10017)) part? as surely that has to be the CS project or the query would not return anything due to the AND statement.
I'm also frustrated by you not being able to get away with:
Project = CS AND status in ("in review", "in test")
as it really should work.
For the record; You are using Jira Cloud...yeah? or......?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Agreed ... not sure why the
(project in (10017)) AND ...
resolved the issue.
Yes! Jira Cloud.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.