Can we create automation rule for Release notes after the Sprint ends?

[Sohail Alam]

Can we create automation rule for Release notes after the Sprint ends?

[Trudy Claspill]

Hello @Sohail Alam 

To what functionality are you referring when you say "Release notes"? What exactly are you trying to accomplish?

[Sohail Alam]

So after the Sprint ends, instead of manually going to release notes and emailing them, can we create an automation rule for that? @Trudy Claspill 

[Trudy Claspill]

The following Solved post is on the topic of automatically emailing Release Notes when a version is Released, with an answer from @Bill Sheboy . I think that solution might also work for you.

https://community.atlassian.com/t5/Jira-Software-questions/How-to-add-Release-Notes-via-Smart-Values-to-an-automated-email/qaq-p/1670838

[Sohail Alam]

I tried this automation rule but did not work.

[Trudy Claspill]

Hello @Sohail Alam 

What were you expecting that rule to do? 

The way you have it constructed it will do the following:

1. When a version is released
2. Check that none of the issues fixed in the version have the Fix Version set to the Released version
3. And if that is true, then send email

The second step does not make any sense. If issues are fixed in the released Version, then the Fix Version field will be set to the released Version.

Your rule does not match the suggestion in the linked post.

The suggestion is to use a rule like this:

1. When a version is released
2. Use the Lookup Issues action to look up the issues that are fixed in that version.
3. Send an email listing the issues from the Lookup Issues action.