nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

First Blood notification

Max Twemlow

Hi All

I would like JIRA to send an email notification which congratulates the assignee on being the first to transition an issue to Complete status for that sprint

i.e. if the issue is the first one with that status, then the assignee gets an email

Is this possible?

Thanks

Accepted answers

Darryl Lee

Hey @Max Twemlow - cool idea. I think I've got it, but haven't tested it.

Basically it triggers when an issue in the project (this is scoped for a single project) transitions to Closed.

It runs a Lookup Issues actions searching for any issues in the same sprint that are Closed. My thinking is that if there is only 1 result (so I check the {{lookupIssues.size}} value, then means you should be the first.

Give it a try, let me know if it works. :-}

Screen Shot 2022-11-29 at 9.33.39 PM.png

All comments

Darryl Lee

Hey @Max Twemlow - cool idea. I think I've got it, but haven't tested it.

Basically it triggers when an issue in the project (this is scoped for a single project) transitions to Closed.

Give it a try, let me know if it works. :-}

Screen Shot 2022-11-29 at 9.33.39 PM.png

Darryl Lee

Ok, tested it and of course found a problem. {{triggerIssue.sprint}} needs to be in quotes, so the JQL should be:

sprint="{{triggerIssue.sprint}}" and status=Closed

I guess if the status you're looking for has two words, that should also be in quotes.

Bill Sheboy

Hi @Max Twemlow -- Welcome to the Atlassian Community!

That is an interesting idea for a scrum team...What about the unintended consequences of rewarding this behavior? Regardless...

Yes, and...to Darryl's suggestion:

It is possible that multiple issues could complete in a short window of time. Rather than check the Lookup Issues result for 1-and-only-1-issue, perhaps add to the JQL for the action ORDER BY Resolved ASC and then compare the trigger issue's key to {{lookupIssues.first.key}} and proceed if it matches the first one to resolution.

Kind regards,
Bill

Darryl Lee

I'm so glad you found this ticket @Bill Sheboy because after I came up with my solution, I started thinking "Wait, is this a good idea?"

(I am totally an admin/implementation guy and unlike Bill have not spent ANY time doing actual Agile coaching/managing/etc. But still, after the technical challenge was finished, I did have some thoughts...)

Re: your other point, about multiple issues...

I think it's highly unlikely that multiple issues would complete at *EXACTLY* the same time, since I'm triggering off of the transition to Complete. I suppose there might enough of a delay in Automation processing that multiple issues could be completed *before* the lookup action does it's search, so sure, your recommendation is a good idea *IF* people start noticing they didn't get their "First Blood" emails.

(I'm not a very defensive programmer. More offensive. :-})