Tasks added after issue is associated to iteration appear on iterations board
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
If you add a task to an issue after that issue has been associated with an iteration, any new tasks added to the issue after it has an iteration will be added to the iteration board as separate items. There's currently no way to remove or hide those tasks from the board without removing the issue from the iteration entirely, leaving a lot of unwanted clutter in some cases.
Steps to reproduce
- In any project, create an iteration (or use an existing one)
- Create an issue, then add it to your iteration
- Look at the iteration board, note the issue appears
- Add a task to your issue while the issue has the iteration assigned
- Look at your iteration board again, see the task appearing separately on the board as if it was a whole other issue
Example Project
I made a public test project here, you can see two items on my iteration board, an issue, and a task that should be a child of the issue https://gitlab.com/gitlab-gold/kchappell/zd339253/-/cadences/26012/iterations/91911
What is the current bug behavior?
Tasks show up separately on the board only if created after an issue has an iteration attached, with no way to hide or remove them
What is the expected correct behavior?
Either it should be possible to hide or remove tasks on the iteration board, or tasks shouldn't newly be added to the iteration board just because the issue they're attached to already was assigned an iteration.
Relevant logs and/or screenshots
Easy to replicate on GitLab.com, here's some screenshots from my example, in little expand-y things because they're big.
Image of my issue with three tasks, the one called "created after iteration set" was created after I added the issue to the iteration
Image of my iteration board, showing the issue itself and the "created after iteration set" task but not the "step 1" or "step 2" tasks
Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
Skipped, recreated on GitLab.com and this looks like a new feature.
Results of GitLab application Check
Skipped, as above.
Possible fixes
I'm no javascript expert, but it looks like this line should update an iteration when a new task is created if the parent item (the issue) has an iteration. So it looks like a match:
My understanding is that this line was added as part of this ongoing effort to make tasks show up in iterations, so it seems like maybe there's a feature flag missing there?
Potential workaround
Since the task only gets added to the iteration if the issue has an iteration already, you can remove the iteration from the issue, add your tasks, then put the iteration back. It's a little annoying but it seems to work okay!