search

blombard / move-to-next-iteration

Automatically move issues to next iteration
MIT License
30 stars 13 forks source link

Does this action respect duration of iterations? #4

Closed igorhrcek closed 7 months ago

igorhrcek commented 8 months ago

👋

I was wondering if this action respects the actual duration of iterations? For example, if I configure a cron to run it weekly on Monday, and we are in the middle of an iteration (that finishes next Monday), is it going to move issues to the next sprint today, or will it do that when it fires next time according to the iteration ending date?

blombard commented 8 months ago

I depends on the input parameters. Specifically iteration and new-iteration. (https://github.com/blombard/move-to-next-iteration?tab=readme-ov-file#iteration)

### iteration
Should be `last` or `current`.

### new-iteration
Should be `current` or `next`.

If you put last in iteration and current in new-iteration then every week it will only put items from the last iteration in the current iteration. (with you weekly cron) => This means, it will do nothing unless you are at the start of a new iteration and in this case, it will move all the items from the previous iteration to the current one.