Open ksierks opened 1 week ago
There is something wrong with the way the Access Level
is being sorted, can you see if you can figure out what is causing it?
There is something wrong with the way the
Access Level
is being sorted, can you see if you can figure out what is causing it?
Maybe I'm misunderstanding, but it's sorting the access level by enum value. Guest (10), Analyst (30), Maintainer (40), and Owner (50) is the sorted order. (least access to most access) I'm assuming the same thing for sorting dates. For example, we don't sort dates as January 18, July 23, June 16 but January 18, June 16, July 23.
I attempted to remove a user
There is something wrong with the way the
Access Level
is being sorted, can you see if you can figure out what is causing it?
Maybe I'm misunderstanding, but it's sorting the access level by enum value. Guest (10), Analyst (30), Maintainer (40), and Owner (50) is the sorted order. (least access to most access) I'm assuming the same thing for sorting dates. For example, we don't sort dates as January 18, July 23, June 16 but January 18, June 16, July 23.
Let's leave it the way it is; that is how GitLab does it. That date example you gave though is slightly different as users would know how dates are supposed to work, whereas access level enum is hidden. A general user does not know that (although I suppose since there are only 4 it is not that difficult to infer).
Covered | Threshold |
---|---|
92.5% | 90% |
What does this PR do and why?
Added sorting and searching to group & project member tables. Fixes #641.
Screenshots or screen recordings
How to set up and validate locally
PR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.