Task #1585
closed
Task #1560: Testing of the product (9.5.0)
FE: role request detail - sort duplicate roles to be removed at the top of the list of roles, in alphabetical order
Added by milus kotisova about 5 years ago.
Updated about 5 years ago.
Description
When there are tens, or even hundreds of roles assigned to the user, it would be convenient if all of the roles highlighted to be removed during de-duplication were listed at (escalated to) the very top of the list of all assigned roles (grouped together with the copies to be persisted). For a quick check, comparison, and survey.
See gif for context.
I'm not sure I understand the rule by which roles are now sorted in the request/task.
Files
- Subject changed from Small feature request (deduplication): sort duplicate roles to be removed at the top of the list of roles, in alphabetical order to FE: role request detail - sort duplicate roles to be removed at the top of the list of roles, in alphabetical order
- Status changed from New to Rejected
- Assignee changed from Ondřej Kopr to milus kotisova
- % Done changed from 0 to 100
The assigned role deduplication is different process - bulk action is so complex for using her for sorting, but attached gif doesn't show 'deduplication' - just simple role concepts for removal assigned roles.
Sorting of assigned roles is designed this way: #1507#note-1
Rows with role concepts for removal assigned roles could be at start of the table, but table will be sorted after clicking on removal button and table "jumps". We wont to have buttons (row) for cancel removal operation in the same place. Maybe, it has some sense, we can reopen ticket if additional benefits will show.
Also available in: Atom
PDF
