In the new filtered navigation introduced here !144907 (merged), we have lost the count of how many users of each type there are. Could we investigate how to include the count in the token only if there is no text filter?
Would it be ok to add count of users to the tokens.
Clever idea @bahek2462774. I can't think of any other place in the product that this is done. I'd like to better understand why these datapoints are important first before I speak more definitively.
@aregnery, before this change, at a first glance an admin was able to see, for example, the amount of pending user without need to navigate to it. However, now, you are force to navigate with the filters to get an estimate of the number of users of each type. I say estimate because we don't show the exact number of users anywhere, and if there are several pages, it is very tedious to do the count.
@eduardosanz yeah I see where you are coming from. I wondering if those numbers must be served in this manner (putting the count in the token).
For example, why not consider adding some of these statistics to the user statistics page on /admin/dashboard/stats ?
Screenshot
Those number must be huge in Gitlab.com.
I know these counters can be tricky. Some places we just cut the count at +1000, so at some point it likely becomes noise. I'm a bit concerned that there might be a performance impact while trying to fetch the count.
At a first glance an admin was able to see, for example, the amount of pending user without need to navigate to it.
Fair point. I believe there are other ways we could explore creating a call-to-action here if it is necessary.
I think it would be important to chat with a few admins to see if these numbers are important for them and if so, what would be the best way to present them.
@bahek2462774 we need a clear problem worth solving to be identified. I think @eduardosanz was on to something that there is a lack of call-to-action for pending approvals, but I wouldn't implement the solution suggested. It goes beyond what the Pajamas design systems offers, so while I'd like to explore other options I don't have capacity.
we have lost the count of how many users of each type there are. Could we investigate how to include the count in the token only if there is no text filter?
@eduardosanz could you help me understand why this is problem? I understand we lost those counts, but it is unclear to me why they are important.
@aregnery I'm interested if reading this comment provides any more insight into whether these counts are useful to customers, and if that changes your mind at all whether we should have them or not.
@hsutor yep I can see how being informed that there are pending requests is important, what I was unsure of is how to address the problem.
Every day some users go into the state "deactivate" so we have few users we can approve. For this I must know the number I could approve
Considering the customer pain point, it sounds like they need to know two things. How many open seats vs how many pending requests. We could do this in several ways which I've highlighted in these screenshots, but I'm not sure which is most impactful. I'm happy to follow your lead, but what do you think?
@vmihai feel free to share these ideas with the customer and let us know if they have any thoughts.
Subscription
Users
User statistics
What's still unclear to me: is it more important to be notified that users are awaiting for approval or that you have seats that you can now allocate.
@aregnery Oo wow, these are nice I think the question of "is it more important to be notified that users are awaiting for approval or that you have seats that you can now allocate." would be a good one for groupprovision - @alex_martin Do you have an issue that already captures the ask of knowing how many seats are left? Maybe we can close this one out against it and include Austin's mocks?
is it more important to be notified that users are awaiting for approval or that you have seats that you can now allocate
I would be curious why it is important to say which question is more important? Is there a trade-off to be had?
If I absolutely had to pick, I would say notified that users are awaiting for approval is more important given that without approval, these folks are blocked from taking action.
Do you have an issue that already captures the ask of knowing how many seats are left? Maybe we can close this one out against it and include Austin's mocks?
We don't have an issue for this yet but I can make one. Trying to find the right home for this work here.
BTW -- if you want to read more about how this "lost the count of how many users of each type there are" has impacted us, this long (but important!) discussion is interesting.
Why interested: We are short of licenses over month the 14500 licenses are not really enough. But the company has no more money to buy additional licenses. So we must track and approve the pending users on daily basis. Every day some users go into the state "deactivate" so we have few users we can approve. For this I must now the number I could approve
Current solution for this problem: n/a
Impact to the customer of not having this: Difficult to hold User Cap with 14250 so we could use 250 licenses
Hannah Sutorchanged title from **Add count on the tokens in the new filtered navigation in Admin Area > Users' to **Add count on the Users in the new filtered navigation in Admin Area > Users'
changed title from **Add count on the tokens in the new filtered navigation in Admin Area > Users' to **Add count on the Users in the new filtered navigation in Admin Area > Users'
Why interested: Customer is using this page on a daily basis to manage user accounts on the platform. Not being able to see the user count on the filters is very inconvenient.
Current solution for this problem: Manually page through the search results to add up page counts.