Configuration and Automation for Sprint-Release Alignment and QG Review Notificati

mahima_bhat January 8, 2025

We have a setup where each release consists of three releases, each having six sprints with a two-week duration. The completion date of the last sprint must align with the release end date. Additionally, we require a Quality Gate (QG) review to occur four days before the last sprint's end date. For this, an automated email/notification should be sent as a reminder to the QG reviewer (assigned as a Project Role).

However, we have identified that in Jira, there is no inherent link between the sprint completion date and the release end date. Furthermore, we need the configuration to dynamically adjust when a new sprint (e.g., a 7th sprint) is added to the release.

Could you please guide us on how to configure this setup and automate the process to ensure:

  1. Sprint completion dates remain linked with the release end date.
  2. Automatic notifications/reminders are sent to the QG reviewer four days prior to the last sprint's end date.
  3. The configuration accommodates additional sprints dynamically without manual intervention.

1 answer

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 9, 2025

Hi @mahima_bhat 

What you describe might be possible using automation rules.  As you clarify your scenario during building the rules, you will learn if there are any gaps in the solution.

 

From what you describe, using the Sprint Created or Sprint Started rule triggers could be used to then create (or update) the release versions with the data alignment.  Again, you would need to build this to confirm how you know when a sprint is within the normal 6 sprints / release versus an extra 7th sprint.

With those rules in place, sending the notifications could use saved filter subscriptions or another email rule with a Scheduled Trigger.

 

Successfully using automation rules requires learning and experimentation.  I recommend mapping out the steps for your process, identify where rules could help, and building / testing them.  And if you run into challenges, post images of your rule and explain what is not working so the community may offer suggestions.  Your Jira Site Admin should also be able to help create the rules.

To get you started on creating your rule, please refer to these documentation and example sources:

 

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
TAGS
AUG Leaders

Atlassian Community Events