tichise
commented
1 month ago This feature addition deviates significantly from the main purpose of this Action, so I forked it and implemented the changes. If there is demand, I will submit a Pull Request. https://github.com/tichise/move-to-next-iteration
I am requesting an enhancement to the move-to-next-iteration library to include a feature that automatically assigns Issues and Pull Requests (PRs) with an unset Iteration to the current Iteration based on specific conditions. This automation would help streamline our workflow and ensure that all tasks and changes are properly tracked within the appropriate Iteration.
Use Case:
In our development process, it is common for Issues and PRs to be created without an assigned Iteration. Manually assigning these to the current Iteration can be time-consuming and prone to errors. Automating this process ensures that all relevant Issues and PRs are included in the current sprint or cycle, enhancing visibility and planning accuracy.
For example, during a sprint planning meeting, developers can create new Issues and PRs based on the discussed tasks. However, if these items do not have an Iteration assigned, they might be overlooked. With this feature, any newly created or existing Issues and PRs that meet the specified conditions will be automatically added to the current Iteration, ensuring they are part of the ongoing work without manual intervention.
This feature would greatly improve efficiency and accuracy in our project management process, reducing the administrative burden on our team.
Thank you for considering this request.