Custom context for filter to apply to a table

Get Help
1

At the moment, users have to approach filters through the filter action above a table.
My users have expressed that they are “not programmers” and “shouldn’t have to deal with” writing their own logic every time they want to filter the data.

I want to set up a filter that they can change without having to enter the filters.

The scenario: we have support tickets being handled through this system. Users can create a ticket, attach either a person or a company (or both) to that ticket, and move it through the workflow stages.

Users have asked that they can be shown a full chronological historical view of every ticket belonging to a company, or an employee of that company.

The filter would be “where company is [company] or person → company is [company]”. This is simple enough for a developer with years experience under their belt, but confusing for people who have not done logic since they left school 30 years earlier.

I can write the view, no issues, but then what happens if they ask for another company? Or they want some other arbitrary filter written to limit tickets to only bugs? I can’t be fixing people’s problems for them, otherwise I won’t get any of my own work done.

So to close out this, is there a way that I can group both company fields together into a dropdown on the main filter bar which users can change as a personal filter? Or is there another way I can get this working so they don’t keep coming to me for reports?

2

Hey, Is this issue still valid for you?

3

Would it not be easier for users to go to the entity view for the Company and see the linked tickets there?
And if they want to see tickets linked to the people from that company, you can add a new relation view to the People relation field, which uses a context filter to show Tickets from the linked People.

At the moment, there is no way to combine collections (or combine context filters) so I don’t know a way to show all Tickets (linked by either route) in the same view, except for manually setting up a filtered view for each Company :frowning:

1 Like
4

If this something really important, you could do it with autolinking and using the devtools to change to an “Or” instead of an “and” and linking by public id’s.

Then you have three relations. One normal ones, and one auto-linked one that has the content from both. Not sure how this scales or looks in practice, but its a potential solution I think. Didn’t test it.

Here’s how: Auto-linking via a to-many relation [workaround]

1 Like