Assigning active sprint in a workflow rule to new production bugs

[Eleanor Kerman]

We would like to automatically assign all production bugs to the active sprint in a JMWE rule.

I wonder how can I know the active sprint out of the box

what I have found as workarounds 

1, run a JQL Query - and populate a custom field "Active sprint" 

Sprint in openSprints() AND Sprint not in futureSprints()

2. Use Automation, and assign via automation

Is there a field name that can be used to set the sprint to the active sprint 

(of course there must be only one active sprint, and not multiple) 

[Nic Brough -Adaptavist- · Accepted solution]

That really is not what sprints are for, and it's not readily supported.  If you're jamming things into a sprint without sizing them and getting the team to commit to dealing with them on a planned basis, you're absolutely not doing scrum or agile development and they're not really sprints any more.  The most you should be doing here is moving them to the top of the backlog so they can be refined and drawn into the next sprint if ready.

I can't work out a way to get this in without using one of the advanced scripting functions.  I think with Automation, you could trigger a "move to the top of the backlog" by issueing a REST call back to the issue, but I don't think you can get it into the active sprint.

[David Fischer]

Hi @Eleanor Kerman 

this Nunjucks expression will return the ID of the (first) active sprint:

{{issue | sprints("active") | first | field("id")}}

You can use it as the Value in a Set Field Value post-function for the Sprint field.

[Slava Gefen]

Thanks. it helped us to leave only active Sprints during creating-new issue by using of a Post-function.