Current Behavior
Team membership of a team that is among the first 10 teams (if ordered alphabetically) is lost if admin adds another team membership that is from table row 11 .. n
Steps to Reproduce
- Create user test
- Create 26 teams, named "A" to "Z"
- Add user to team A --> verify OK
- click on the "+" icon to add user to another team.
- Find team "X" by flipping through the pages (">") or by choosing a page size of 50
- Select X and click "Select"
- Verify that now user test is a member of X but no longer of A
Expected Behavior
User test should be a member of both, A and X
Dependency-Track Version
5.x
Browser
Microsoft Edge
Checklist
Vague suspicion (without having looked at the code!): In v4.x, the UI state was merged with the backend state (if UI had "X" and backend had "A", then the result was "A, X", but in v5.x it seems like the UI replaces the prior backend state with its current UI state, which is incomplete after using the pagination controls --> data is lost
Current Behavior
Team membership of a team that is among the first 10 teams (if ordered alphabetically) is lost if admin adds another team membership that is from table row 11 .. n
Steps to Reproduce
Expected Behavior
User test should be a member of both, A and X
Dependency-Track Version
5.x
Browser
Microsoft Edge
Checklist
Vague suspicion (without having looked at the code!): In v4.x, the UI state was merged with the backend state (if UI had "X" and backend had "A", then the result was "A, X", but in v5.x it seems like the UI replaces the prior backend state with its current UI state, which is incomplete after using the pagination controls --> data is lost