How to keep Quick Filters on Work Management Projects from suggesting ALL TEH USERS!?

Question

Hey all,

The Work Management board, list, calendar, and timeline tabs all share this Quick Filter option. Among its many quirks appears to be suggesting everyone in your directory in alphabetical order automatically for Assignee or Reporter.

Since the migration tool makes users for all of your content, and we're using a service to manage users who actually have access to the application, we have 200+ users in the directory that are just to provide names for links so that everything doesn't say "Unknown User"... but only 20+ users in this system at the moment, and only 6 or so added to this project by roles. The issues are made and assigned with those six users... so dumbly I assumed the filter would be auto-filled by the issues in the project...

You know, just like the top of the same page is for presence and the other way you can filter for Assignees...

But no.

It doesn't matter if they are on the issues in the project.

It doesn't matter if the users are add-on users, assigned a role to the project, what their status is, or whether they are even assigned to and have access to the Cloud product.

Nope, it just plops 2 lines of irrelevant people missing profile icons onto your screen, rendering the feature useless to us.

Is there any way to limit the suggestions on the filters without breaking the ability to find users to assign to issues as well?

I'm hoping I'm just missing something stupid that I needed to check off and I can fix this for my users quickly.

Dom_thxc7k · Answer

@Trudy P Claspill Thank you for the validation.

There's a point where this kind of thing is amateur-hour nonsense that we should get all get money back for.

Literally the logical filter functionality is implemented on the same functional space. Above the content, it shows users who visit the project really nicely. What do you you know! Clicking on them... *gasp* filters by Assigned to that user! It actually works a treat! Combines with Presence, even.

Yet in the same breath, we have the worst options in the Filters. Between saved filters in the Quick Filter being hardcoded as automatically shared with all roles (yikes!) and the painful implementations of the UX, it's like a UI bear trap for your patience.

The only recourse is this multi-year plod towards getting votes enough to maybe get someone to acknowledge that multiple people let the crappiest work through to production?

I'm offended that anyone would think this kind of experience is worth money from customers. There's no world where this should be even an MVP consideration - that's not even useful as a filter, let alone a quick filter. It's actively more painful than if you left it as a type-in field.

So there's Bugs and there's Suggestions. Do you know where we can lodge tickets for "This isn't even close to Acceptance Criteria of any sort outside of a Snake-Oil Salesman level of rip-off, please address immediately"? because this processes and experience is the dirt worst.

*heavy sigh*

Trudy P Claspill · Answer

Hello @Dom

You are not missing anything. That is the current functionality of the filter.

There is a change request about it, to which you can add your vote/comments.

https://jira.atlassian.com/browse/JWMCLOUD-590