Adding issues with a due date where sprint is planned

[Jofre Bosch]

Hi all,

I usually create an sprint for week, until end of year.

I have a lot of issues coming in and they are created constantly. Every time, for each issue, I link them with the correct sprint, depending on its due date.

I would like to know if there is a way to include an issue automatically (using automation rules) inside am "already-planned" sprint (with its start and end dates) once the issue has the Due Date filled/changed.

An user case:

- I have an Sprint (Nov21_03) that starts on 8 November and ends on 15 November. It's not the "Active Sprint", not even the "Next sprint".

- I create an issue where I fill the Due Date field with "16 November 2021". (So it should be inside the Nov21_03 sprint).

What I expect (Automation Rule):

- Jira "understands" that the Due Date of that issue type is "inside" the start and end date of a planned Sprint so the system assign automatically the issue with the correct sprint.

Thank you very much,

Jofre

[Bill Sheboy]

Hi @Jofre Bosch 

Would you please explain how your team is using Scrum?  Teams use Sprint Planning to confirm the goal they plan to achieve, the work items to meet that goal, and a plan to implement those work items.  This automation idea seems like it could create a sprint backlog the team has not seen or planned, leading to the unintended side-effects of failing to meet the goal, carrying over work, etc..

Next, please consider these questions before you start building the rule:

• The dates in your example's created issue do not fit in your example sprint.  How exactly do you determine the appropriate sprint?
• Do the due dates *ever* change for an issue?  If so, what do you expect to happen?
• Are work items *ever* larger than can fit in a sprint?  If so, in which sprint would you place them for start of work?
• What would you expect to happen when the target sprint is not available?

Now regarding automation: I suspect your use case may be possible and it may not be trivial.  After answering the above, it would at least include:

• from the created issue Due Date, dynamically determine the appropriate sprint Name using text and date/time functions
• for the sprint name, determine if the sprint exists, is not in-progress, and is not already completed.  (Probably requires a REST API call to gather all possible sprints, which cannot be done with built-in automation or JQL.)
• edit the sprint field for the issue

Kind regards,
Bill