Auto Assign Sprint

[Eric Percival]

I wonder if anyone from the community can help me with the following question:

We are currently doing 1 week sprints (max 10 issues per sprint) and I have been tasked with coming up with a way to auto assign a sprint based on a priority score that the ticket has. 

We are using a Foxly plugin to set the priority score. Assuming all the tickets have a priority score and all the sprints are created for the rest of the year. The issue I am running into is I am not sure how how iterate from sprint 1 to sprint 2 to sprint 3 once each sprint has its 10 issues assigned to the sprint. 

Even if I were to say I wont actually assign it to a sprint but rather set a custom field what would be the iteration logic to move from one sprint to the next after I have reached the 10 issue capacity?

Any ideas? 

[Brant Schroeder · Accepted solution]

@Eric Percival Welcome to the Atlassian community

I am not aware of a delivered way to do what you are asking to do nor do I know of any apps that provide that functionality.  Jira is built on Agile principles and auto setting up sprints does not really follow that methodology.  Here is some helpful information https://www.atlassian.com/agile/tutorials 

[Eric Percival]

@Brant Schroeder Hi Brant thank you for the quick response. Do you know of any logic that I would be able to use to iterate up (counting by 10) and populating a custom field?

I was thinking I create a custom field with the weeks of the year and then I would have logic that populates this custom field with week 1 on 10 tickets week 2 on the next 10 tickets and so on. Any ideas?

I agree this is not Agile and we don't want to concretely put it into a sprint but we do want to do some level of forecasting should the priority of the tickets remain the same from week to week. 

[Brant Schroeder]

@Eric Percival You could easily create a filter and export the issues into CSV, update the field incrementally and then import via CSV to update the custom field.  That seems like the simplest way to accomplish what you are trying to do.  

[Nikki Zavadska _Appfire_]

Agreed with @Brant Schroeder that this is the best approach in this particular scenario.

Thank you for the suggestion Brant!

[Nikki Zavadska _Appfire_]

Hi @Eric Percival ,

I'm Nikki from Jexo - the makers of the Foxly app. I'm glad you're enjoying using Foxly for your backlog prioritization and sharing this really interesting use case.

I was just having a look at the automation rules and found a trigger that might be interesting for you -> "Sprint created"

Using this you could setup an automation to assign issues automaticaly based on priority score when new sprint is created.

However I'm affraid it's not possible to filter out the top 10 issues using JQL.

Workaround could be to set the intervals for the Priority Score (eg. "Priority Score" <= "200" AND "Priority Score" >= "1000") but that doesn't guarantie number of returned issues.

To conclude, looking at this specific situation and if you're planning to prioritize and forecast multiple sprints ahead using CSV import as @Brant Schroeder mentioned to update Sprint field will be the easiest option 🙌