Jira Automation Release Version + Send Message in Slack

[Vanessa]

Hello, 

we are using an automation in Jira

-> if a version is released, the issue will be looked up and a message will be posted in Slack and Microsoft Teams.

It worked the whole time, now the problem appeared that the message always contains a different version (as it should) but the same issue, even though this certain Issue is not tagged with the Version.

Anyone an idea what is wrong?

We are using Jira Cloud and it is a company managed project.

Here is our Automation:

Thank you so much in advance!

- Vanessa

[Stefan Salzl · Accepted solution]

Hi @Vanessa 

Could you please add a screenshot showing the audit log?

Best
Stefan

[Vanessa]

Hello @Stefan Salzl 

Yes sure, this is the audit log from the day we faced the issue.
The config change was only that we disabled it once and enabled it again.

[Stefan Salzl]

hi @Vanessa ,

sorry for my incomplete requirement. Could you please show me the output of an audit log to see what gets processed?

Best
Stefan

[Vanessa]

Hello @Stefan Salzl 

No Problem at all!

Is this alright?

[Stefan Salzl]

Hi @Vanessa 

It seems the JQL for the lookupIssue isn´t correct. I couldn´t validate the JQL with latestReleasedVersion. 

Please try to add () --> fixVersion = latestReleasedVersion()

That worked on my site (see screenshot)

Best

Stefan

[Vanessa]

Hi @Stefan Salzl 

I think we already had the same JQL in there.
It is still only showing me this one Issue.

Is it maybe the case, that it is always showing me this one certain issue because it has the latest release version and all other issues have been released a few minutes before that?

If so, would you know how to adjust the automation?

So if I release a version, it should look up this exact issue and post this in Slack and Teams. 

I am sorry for the inconvenience,

all the best

-Vanessa

[Stefan Salzl]

mkay....found the solution (which to me is reeeally silly but it´s documented in the documentation):

Note, the "latest" is determined by the ordering assigned to the versions, not by actual Version Due Dates.

Which means: depending of your ordering in the versions/release page the latestReleasedVersion() will always pick the one from the very top.

Nevertheless i was thinking about an even more fitting solution in your case:
As you definitly would like to stick to the version you just released it would be more acurate to use the version smartvalue directly in your JQL. Thus you REALLY refer to the version that triggered the rule (which is exactly what you would like to see i guess)

[Stefan Salzl]

Hi @Vanessa ,

Any update on this? could you test the suggested solution?

Please let me know if this works for you and in case your problem is solved please consider to accept the answer so this question is marked "solved" and other people in need can find the solution easier.

Best
Stefan

[Vanessa]

Hi @Stefan Salzl 

thank you for your patience!
I just tested it and it works perfectly fine! :) 

Thank you so much for the help through the whole process.

All the best,

Vanessa 

[Stefan Salzl]

Hi @Vanessa ,

Awesome. So happy it works now.

You are welcome. It was my pleasure. That´s what the community is for ;)

Best
Stefan