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; } } }

Incremental Values within Sprint Name

Ponce de Leon, Eduardo

Hi all,

Is it possible to define names with incremental Values. Currently at my company de sprint nomenclature is as belongs:

Sierra Spr32: 5/Feb - 18/Feb

Sierra Spr33: 19/Feb - 4/Mar

I have been looking into when a Sprint Starts...send an email to the scrum master to review the upcoming JIRAs that are already in the upcoming sprint to verify that all the requirements are in place. This has been hard due since I cannot get the dates of the current and following sprints.

So far this is what I have been able to accomplish so far

Sprint Name

Sprint Start/End Date

I am struggling to search for the next future sprint by name considering the naming convention

Sierra Spr##

2025-02-17 14_39_00-Rule builder - Automation - MRD Workbook - Jira.png

This is the body of my email where I get the results of my variables.

2025-02-17 14_42_56-Inbox - eponcedeleon@KPMG.com - Outlook.png

Please let me know if there are any suggestions to seach by Sprint name "

Sierra Spr##

Accepted answers

Bill Sheboy

Hi @Ponce de Leon, Eduardo -- Welcome to the Atlassian Community!

Have you started an automation rule to do this?

If so, and it is not working as expected, please post the following to provide context for the community to help:

an image of the complete rule in one single image for continuity
an image of the audit log details showing the rule execution (with all areas expanded)
explain what is not working as expected and why you believe that to be the case

If you have not started a rule yet, I encourage you to try to do so. Successfully using automation requires learning and experimentation.

To help you get started, please consider:

Do these future sprints already exist?
Are there already issues assigned to the future sprints?

If the sprints exist and there are issues assigned, an automation rule could be triggered on the sprint started and use JQL to find them to notify the product owner to check them for readiness. If the sprints exist but there are no issues, the REST API could be used to find the sprints.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Ponce de Leon, Eduardo -- Welcome to the Atlassian Community!

Have you started an automation rule to do this?

If so, and it is not working as expected, please post the following to provide context for the community to help:

an image of the complete rule in one single image for continuity
an image of the audit log details showing the rule execution (with all areas expanded)
explain what is not working as expected and why you believe that to be the case

If you have not started a rule yet, I encourage you to try to do so. Successfully using automation requires learning and experimentation.

To help you get started, please consider:

Do these future sprints already exist?
Are there already issues assigned to the future sprints?

Kind regards,
Bill

Ponce de Leon, Eduardo

Hi Bill,

thank you for the response, here is mine!

To help you get started, please consider:

Do these future sprints already exist? YES
Are there already issues assigned to the future sprints? YES

-This is my ultimaate goal, I have added a better description and screenshot of my rule, but I am not stuck at the poing of searching for the future sprint.

Bill Sheboy

Thanks for that information, and...

Using the information from the current sprint name, you could extract the number "32" using text functions: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/
That number could be converted to a number with the function asNumber: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#asNumber
And then that could be incremented with plus(1): https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/#Plus-Minus
Finally, the could be combined with the date values you found for the next sprint dates to make a sprint name for searching: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-format---

If you are still using the sprint started trigger, and the sprints are 14 days long, the name of the next sprint would be:

Sierra Spr{{sprint.name.substringBetween("Spr", ":").asNumber.plus(1)}}: {{sprint.startDate.plusDays(14).format("d/MMM")}} - {{sprint.endDate.plusDays(14).format("d/MMM")}}

That could be saved in a variable, perhaps named varNextSprintName, and used with JQL to find the issues using Lookup Issues:

project = yourProjectName AND sprint = "{{varNextSprintName}}"

Ponce de Leon, Eduardo

Hi @Bill Sheboy thank you for your response. I was able to adjust it to my needs and working perfectly. But now I am running into an issue where now that I have the sprint i am trying to search for the items on that Sprint related to a user and send them an email.

For some reason my variable to get the reporter name is not working.

I have tried the 2 below combinations with no luck!

2025-02-18 10_15_36-Audit log - Automation - MRD Workbook - Jira.png 2025-02-18 10_13_19-Audit log - Automation - MRD Workbook - Jira.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

cloud-automation