Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automatically push tickets based on capacity

Mark G January 31, 2023

Hi Awesome jira community,

       I've been falling in love with how to automate out the project planning aspects of sprints. I want to create an automation that automatically pushes tickets to sprints based on individuals capactiy.

      Specifically I have my engineers complete 12 points per sprint. I want when tickets reach over 12 points for an assigned person per sprint that the last tickets added or lowest priority ones get pushed to the next sprint. 

      Any help on this would be awesome! 

 

1 answer

1 accepted

1 vote
Answer accepted
Kian Stack Mumo Systems
Community Champion
February 10, 2023

@mgilpatrick

I got something put together that sort of works, but I'm not sure it fully meets your needs. Hopefully this will get the wheels turning though!

Screen Shot 2023-02-10 at 2.17.52 PM.png

 

Basically we tell it that if an assignee in a sprint has more than the specified number of story points, pull all issues in the current sprint assigned to the user. Take the one that is ranked the lowest, and then push that one into the next sprint.

It only works if the current sprint is active, AND you have another sprint ready to go AND you are modifying the assignees. You could build a second rule to also trigger when the Sprint value is changed for an issue.

 

Hopefully this is somewhat helpful, but I found it an interesting problem to consider at the very least and share what I found!

Mark G February 10, 2023

This is so great tbh. Just to help include more to the problem.

- I typically map out sprints for 6 months, each sprint is 2 weeks. so I'm really trying to get something to crawl through each sprint and keep pushing out from the top (earliest sprint ) to the next sprint and then again.

- Ideally every issue is in the next sprint and it follows FIFO method as it goes to additional sprints 

 

Basically I'll show an example and an ideal input and output 

Input

[Engineer A's board]

10 story points per sprint 

 

Sprint 1

Task A (5 pnts) 

Task B  (5 pnts) 

Task C  (5 pnts) 

 

Sprint 2

Task D (5 pnts) 

Task E (8 Pnts)

 

Sprint 3

Task F  (5 pnts) 

 

Sprint 4 

Task G  (5 pnts) 

 

 

Basically I'll show an example and an ideal input and output 

Input

[Engineer A's board]

10 story points per sprint 

 

Sprint 1

Task A (5 pnts) 

Task B  (5 pnts) 

 

 

Sprint 2

Task C  (5 pnts

Task D (5 pnts) 

 

 

Sprint 3

Task E (8 Pnts)

 

 

Sprint 4 

Task F  (5 pnts) 

Task G  (5 pnts) 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events