Automatically assign an issue to a sprint

[Eddie Hobart]

I'm trying to create an automation rule or something similar that automatically assigns a certain ticket type to an active sprint.

Specifically, the permissions setup we're working with prevents devs from adding tickets to the active sprint (the PO or SM has that power). However we have a ticket type "sprint defect" that by definition should be worked on in the same sprint period as it's created (devs can create tickets). Since the dev can't add the issue themself, there's a delay getting it into the sprint and on the active board. 

I'm hoping that with the scenario below, it'll be possible to setup some sort of logic to achieve this.

1. Sprint Defects are created when a Story has a problem in testing
2. The Story is in an active sprint
3. The Sprint Defect will be linked to the Story
4. The Sprint Defect will be in the same active sprint as the linked Story

Given the linked relationship with a story that's already in an active sprint, is there something that can be setup to achieve step 4 without manual assignment?

[John Funk]

Hi Eddie,

One option might be to create a manual automation rule that runs from the Story. You could let anyone run the rule and have a prompt for the summary and link it to the story. 

Another option would be to create it as a sub-task under the Story. 

A third option would be to automatically add it to the open Sprint when the Sprint Defect work item is created, but you would have to figure out how to link it to the appropriate story. 

[Eddie Hobart]

Hi John,

Thanks for suggesting some ideas. 

1. So, a manual trigger could be setup and that rule would bypass the permissions and allow a dev to have the defect be assigned to a sprint? How does that work?

2. Sub-task won't work for my situation, but thanks.

3. How does the automation script know what sprint to add it to? There is more than one active sprint in Jira (other projects). Linking the issue is done manually already without issue.

[Bill Sheboy]

Hi @Eddie Hobart 

Yes, and...to the suggestions from @John Funk 

Do you have multiple active sprints at the same time in the same project?  If so, an automation rule could be triggered on linking the "Sprint Defect" to the Story (assuming those are the specific work item types involved) and then use list filtering on the Story's sprint field to find the correct one to use.

For example:

{{#issue.sprint}}{{#if(equals(state, "active"))}}{{id}}{{/}}{{/}}

Kind regards,
Bill