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

Ticket assignment to defined sprints

goekce.vardar1

Hello,

My team has some tasks that are repetitive and don't need conventional sprint planing. I just need those tickets to be sent to the corresponding sprints.

It means a ticket would have a due date and the newly created ticket would just be automatically assigned to that sprint. Sprints for a whole year can be created, but tickets either come on later or their dates get changed. So the trigger is not the created sprint but the created ticket or the ticket with a date change.

How could I realize this?

Thank you very much!

Accepted answers

Vishal Biyani_2pr07j

@goekce.vardar1

As you are talking about 50+ sprints, I am assuming you have 1 week sprint.

You will have to write two rules as there are two triggers

one for Create Issue and one for field change (due date).

Create a smart variable say varSprintName and extract required values like this

Sprint{{issue.duedate.weekOfYear}}.{{issue.duedate.year}}

or whatever is your sprint naming convention

For due date of 27th March 2025, you will get Sprint13.2025

Then you can edit the issue for Sprint and assign it the value using varSprintName

See if this works for you.

All comments

Tuncay Senturk _Snapbytes_

Hi @goekce.vardar1

As far as I understand, you want to automatically assign tickets to the correct sprint based on their due date.

You can use Jira Automation to achieve this. afaik, Automation doesn't let you dynamically search which sprint contains a date but you can use if-else conditions for each sprint as a workaround.

use trigger as the field value changed: Due date (or issue created)

In the action you will have if-else blocks to check the due date range and assign the matching sprint

(action -> Edit Issues -> Field: Sprint -> Value: Sprint 5)

IF Due Date is after 2025-04-01 AND before 2025-04-14 then Assign to Sprint “Sprint 4”
IF Due Date is after 2025-04-15 AND before 2025-04-28 then Assign to Sprint “Sprint 5”

I hope that helps

goekce.vardar1

Hi @Tuncay Senturk _Snapbytes_

thank you for your suggestion. But the problem is I'd like to do this for a whole year and then I'd have to have roundabout 50 iterations. This might be a big performance problem for the automation. And I would have to do it every year new.

What I was thinking is, I have a dute date in my ticket and I can take the ww.yy from my ticket and the sprint names contain this format as well. So I feel like this should be possible but I don't know how

Vishal Biyani_2pr07j

@goekce.vardar1

As you are talking about 50+ sprints, I am assuming you have 1 week sprint.

You will have to write two rules as there are two triggers

one for Create Issue and one for field change (due date).

Create a smart variable say varSprintName and extract required values like this

Sprint{{issue.duedate.weekOfYear}}.{{issue.duedate.year}}

or whatever is your sprint naming convention

For due date of 27th March 2025, you will get Sprint13.2025

Then you can edit the issue for Sprint and assign it the value using varSprintName

See if this works for you.

goekce.vardar1

Hi @Vishal Biyani

this was my first idea as well. But the problem is, I can't set the Sprint as a string but I need to select a sprint with this name from the list.

If I do it the way you described, I get the error that my sprint Id needs to be a number. So what I technically need is someway that variable to be found in the sprint name and then chosen.

Do you think there is possibilty for this?

Vishal Biyani_2pr07j

Now that the approach to get sprint name is correct,

next step will be

send a web request to get all the sprints
using smart filter get the id
edit the issue

Refer this link and see if you are able to make progress

https://community.atlassian.com/forums/Jira-questions/Re-How-to-change-sprint-in-JIRA-automation-based-on-name/qaq-p/2654509/comment-id/935659#M935659

Vishal Biyani_2pr07j

@goekce.vardar1

Have you been able to make progress?

Once you have successful webresponse, you will need to use Advanced Branch to iterate over each sprint value returned using smart value {{webResponse.body.values}}.

Would like to see what rule you have written so far and I can fill the missing pieces.