Add issues to a closed iteration

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Release notes

Problem to solve

In case of automated iteration cadence, issues are moved to the next iteration at the end of an iteration. However, it could be that the last MR on an issue was also reviewed and approved but just not merged. We don't want to move all such issues to a new iteration. And if those issues have been automatically moved to the next iteration then I would expect a practical way to assign them to the previous iteration.

Proposal

I have multiple proposals to be evaluated, and I do not mind the cheapest option for now, but I think 3 is a good long term option for several agile teams.

1. Make /iteration quick action work similar to /milestone (#324298 (closed))
2. Allow changing to 1 previous iteration via UI
3. Create a separate named pseudo iteration called previous_iteration (also next_iteration)
   1. This can be used with multiple boards to be tracked: one for previous iteration and one for current iteration, so it is never a problem.
   2. This can be used in issues search: so devs can easily lookup without having to figure out the iteration number.

Intended users

• Delaney (Development Team Lead)
• Sasha (Software Developer)

Feature Usage Metrics