Repository navigation
refactor(teams_selection): centralize team selection in TeamSelectionService - #592
sawankshrma wants to merge 6 commits into
Conversation
|
This PR has been automatically marked as |
|
Hi, what is the status? |
- add move up/down buttons in selectable list edit mode - track team renames explicitly so reordering isn't treated as a rename - show teams in configured order in heatmap and team selection component
51bc7ca to
0ae4a2e
Compare
Hi @wurstbrot, @vbakke, This PR is now ready to review :) |
|
Thank you @sawankshrma! This is so much better! Finally we can re-order the Teams and Groups 😃 🙏 Sorry for the late review. I mistook the email from GitLab as an issue that had gone stale. I did find some minor bugs, and some bugs in the original specification. I'll split them up in separate posts, to easy the discussion |
Missing from specificationLooks like I missed a couple of places where the Global Team Selection Object (GTSO? : ) should take effect:
|
Report page
|
Close the menuIt took me a while to figure out what the Please close the menu-warning meant. I thought maybe it was a menu in Chrome itself, but could not find one. 😄 I agree that having the menu in the print out is undesirable. I suggest that we just automatically close the Menu for the user if it is open. I don't see that as too obtrusive. The user can just hit the burger menu again if they want the menu back. Any other views, @sawankshrma, @wurstbrot ? |

Adds a
TeamSelectionServiceas the single source of truth for the active team filter, used by the heatmap, report page/modal, and evidence components. RemovesselectedTeamsfromReportConfig(previously stored insidelocalStorage, now only persists per-session)Changes:
selectedTeams,effectiveTeams,selectedGroupName, andisAllSelectedas computed signals.effect()selectAllTeams()/deselectAllTeams()/selectGroup()just emit rather than mutate local state.Follow-up changes: (Addersing Issue: #588)
Teams & Groups can now be reordered with up/down controls in edit mode. Team order is stored in the existing teams array; group order is preserved by rebuilding the group mapping in the selected order.
Team rename handling now tracks explicit rename actions instead of inferring renames from list positions. This prevents a reorder from being treated as a rename and incorrectly moving progress or evidence data.
Deleting a team continues to remove it only from the active team/group configuration; its stored progress and evidence is preserved by re-creating the same team name.