Automatically Move to Next Iteration #16222
-
|
At the end of an iteration it would be great if incomplete issues automatically got moved to the next iteration. Without this issues either get lost because filters only show current iteration or we have to manually move the issues over. In the short term this functionality could be implemented with a GitHub action that was invoked at the start/end of an iteration. |
Beta Was this translation helpful? Give feedback.
Replies: 22 comments 10 replies
-
|
Surprised this hasn't had more comment - it's too easy to lose sight of incomplete issues from previous iterations at the moment, in my experience. It would be great to be able to decide what to do with outstanding issues when an iteration 'closes'. |
Beta Was this translation helpful? Give feedback.
-
|
Would also really like this feature and would like to know that it was carried over from the previous iteration. I currently have to keep track of this manually and within a separate spreadsheet. |
Beta Was this translation helpful? Give feedback.
-
|
Also this, every two weeks we have to move any open tasks not 'done' in the past iteration, it should do this automatically. |
Beta Was this translation helpful? Give feedback.
-
|
That this is not answered yet by GH is very sad imho. |
Beta Was this translation helpful? Give feedback.
-
|
Assuming I have an iteration field called "Sprint" This would be very useful. If the workflows feature was a bit more advanced, it could be easily done:
Would also be useful:
|
Beta Was this translation helpful? Give feedback.
-
|
Since Github has other fish to fry, I made my own Github action: https://github.com/marketplace/actions/move-to-next-iteration |
Beta Was this translation helpful? Give feedback.
-
|
Agreed this would be a very useful feature. One more reason to move back to Jira atm... |
Beta Was this translation helpful? Give feedback.
-
|
Also agreed this would help avoid Issues slipping through the cracks. |
Beta Was this translation helpful? Give feedback.
-
|
Can't believe this is not built in |
Beta Was this translation helpful? Give feedback.
-
|
Adding a +1 for this feature request! Or a view that shows all issues which haven't rolled over to make it easy to select them. |
Beta Was this translation helpful? Give feedback.
-
|
Adding a +1 for this feature request. Now moving tickets one by one. |
Beta Was this translation helpful? Give feedback.
-
|
+1 - thanks to @blombard for making a github action in the meantime - this should be native... |
Beta Was this translation helpful? Give feedback.
-
|
Its September 2024 and I would upvote for this feature to be native. |
Beta Was this translation helpful? Give feedback.
-
|
This is embarrassing for project planning |
Beta Was this translation helpful? Give feedback.
-
|
will there be an update for node20? |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
FWIW, you can show all issues that (1) have an iteration assigned and (2) the assigned iteration is either current iteration or a previous one with I agree that automatically moving the iteration forward should be an available feature, though. |
Beta Was this translation helpful? Give feedback.
-
|
I was planning to use Github projects for spring planning but this is a real deal breaker, I don't want to focus on moving stuff to sprints, I want to focus on shipping products. +1 Please implement this |
Beta Was this translation helpful? Give feedback.
-
|
Sad that this ticket is still open after 3 year. Feels like a basic feature. There is indeed an workaround action, but within the company we cannot use unverified actions. So the only solution would be to implement it ourselves. I think a lot of enterprise customers would benefit from this feature. |
Beta Was this translation helpful? Give feedback.
-
|
I don't have the impression that anyone is still working on Projects at Github. Last product update is from over a year ago, looks quite abandoned to me tbh. |
Beta Was this translation helpful? Give feedback.
-
|
I wrote an entire Github Actions to re-implement how https://www.pivotaltracker.com/ does XP programming and calculating iterations and running velocity to move stories appropriate. Will maybe release publically but we ended up writing this all by hand. |
Beta Was this translation helpful? Give feedback.
-
|
This isn't fully automated, but we released an update here - https://github.blog/changelog/2026-03-05-hierarchy-view-improvements-and-file-uploads-in-issue-forms/#move-to-next-iteration-in-bulk - that will make it much quicker to move these over |
Beta Was this translation helpful? Give feedback.
This isn't fully automated, but we released an update here - https://github.blog/changelog/2026-03-05-hierarchy-view-improvements-and-file-uploads-in-issue-forms/#move-to-next-iteration-in-bulk - that will make it much quicker to move these over