Feedback Needed: Quick filters

[kalman]

@Mircea_Braescu

• The option to share the URL to a particular board with and with a particular quick filter enabled

• There was a “show/hide quick filters buttons” option which came in handy for boards where there were a lot of quick filters

When you share the view, the default quick filters will apply. Is this what you are looking for, or would you like to share specific filter settings (differnet from the default) including personal filters?

Showing or hiding the quick filter buttons is out of the scope. We would collect more feedback on this feature first.

[Ivan]

The second one.

For example, I have a filter to hide old finished or discarded tasks to avoid cluttering the views.

I want this filter in a table, a list or tables with further filters (for some teams).

Also when I start a new project (space) I want to use the same filter. A solution like airtable were you copy colors and filters would be super useful.

Same for colors, I need to create the same manually between views or new projects.

[Mircea_Braescu]

@kalman

Would you like to ensure that different Quick filters are turned ON when use visit the view based on the different links?

Exactly
This is pretty much how jira does it:
https://code11.atlassian.net/jira/software/c/projects/ACME/boards/335?quickFilter=932

[kalman]

@Mircea_Braescu

Let’s say that there are 3 global filters for a board: A, B, C
I want to be able to share links such as

• …/some-board?filter=A
• …/some-board?filter=B
• …/some-board?filter=C

Would you like to ensure that different Quick filters are turned ON when use visit the view based on the different links?

no, this is not part of the scope, but I will add as a request to the list. thanks.

[ccollins]

This looks great!! I’m really excited for this feature. My only concern was covered by the roadmap description “…and the default value of the pin is OFF”. The video shows the default as ON, but I’m hoping that is only for the creator? And then default OFF for everyone else? I really hope this is the case.

@kalman

@YvetteLans

@kalman are context/relation views in scope? Or not?

unfortunately, quick filters on relation views is not part of the scope.

I understand this is not in the initial scope. But add my vote to figuring out a way to add them eventually. We use a lot of context/relation views and I would love this.

[kalman]

@ccollins

This looks great!! I’m really excited for this feature. My only concern was covered by the roadmap description “…and the default value of the pin is OFF”. The video shows the default as ON, but I’m hoping that is only for the creator? And then default OFF for everyone else? I really hope this is the case.

I believe that part of the description is misleading or simply incorrect. There is no default value. The creator will decide what the default value should be. A disabled pinned filter becomes a Quick filter, which is turned OFF by default. I hope this is an expected behabour.

I will correct the description right away.
Thank you for reading through it.

[JoelH]

This looks great. I absolutely love Jira’s quick filters and this would really cut down on Views and make it easier for me to work in Fibery. Looking at the design it seems a bit similar to how it works in Jira, but I’m unsure if I correctly understand the design.

Given my examples and statements below, is my understanding correct?

“Base filter”
As a creator, I have set up a View of showing Tasks that I put some “base” filter on (=filters that is not “pinned” in the Filter Pop-up):

• Task Status is Next Up, In Progress
• Team is TeamA

So essentially the “base filter” is what we have today. Then if I add and apply Quick-filters, their conditions will apply onto this “base” and only filter i.e. “remove” Tasks from the base filter. I can only have a single “Base filter” per View, as today.

I add these Quick-filters by creating these filters and Pinning+naming them:

A Named filter “TeamB”

• Team is TeamB

B Named filter: “Sara”

• Task assignee contains any of: Sara

C Named filter “Peter”:

• Task assignee contains any of: Peter

D Named filter “Prio”:

• Task priority is High

E Named filter: “My upcoming”

• Task assignee contains Me
• Due date is within the next week OR Due date is within the past week

Given this base and quick filters, this is the behavior I would get - ?

By default since I have not applied any Quick-filter, all Quick-filters are OFF on my first visit.

1. If multiple filters are ON, each Quick-filter’s condition will be joined with an AND between them
2. Quick-filter “Team B” ON will be useless, since base filter is already filtering Team is TeamA. My mistake, I should just remove it
3. Quick-filter “Sara” ON and “Prio” ON will show only tasks where Sara is in the assignee field and of those, only the ones that have prio High
4. Quick-filter “Sara” ON and “Magnus” ON will only show tasks where Sara and Magnus are both in the assignee field, i.e. not tasks individually assigned to Sara OR to Magnus. If I am looking and Sara’s assigned tasks and want to check out Magnus, I’d first toggle “Sara” OFF and “Magnus” ON. If I wanted to have a Quick-filter that shows tasks assigned to either Sara or Magnus, I’d create a new Quick filter with Task assignee is Sara OR Task assignee is Magnus, and use that
5. Quick-filter “My upcoming” ON can be a quick filter even though its made up of multiple conditions (e.g. using a group?)

[kalman]

@JoelH

Given this base and quick filters, this is the behavior I would get - ?

By default since I have not applied any Quick-filter, all Quick-filters are OFF on my first visit.

1. If multiple filters are ON, each Quick-filter’s condition will be joined with an AND between them AND the Base filter
2. Correct
3. Correct
4. I am not sure where Magnus came into the picture but sounds corrrect, if you have a Magnus filter as well.
5. Correct

[Chr1sG]

@kalman

I am not sure where Magnus came into the picture but sounds corrrect, if you have a Magnus filter as well.

I think Magnus is Peter’s alter ego

[JoelH]

Just the behavior I wanted then. Looking forward to trying it out later!

Yeah, Peter = Magnus, the team manager just mixed up their names

[HereBeBeasties]

Scope creep, but one of the most useful things you can do with quick filters in JIRA is with some JQL like currentUser() IN assignees. (Or whatever the syntax is, I’m glad to say it’s been a while!)

It’d be great if you could add a currentUser() equivalent for User filters more generally. It’s one of the few things we really miss from the more general JQL filter syntax. It’d help with per-person reports, personal task boards, etc.

(That and more flexible date options in filters and functions.)

[kalman]

@HereBeBeasties

It’d be great if you could add a currentUser() equivalent for User filters more generally. It’s one of the few things we really miss from the more general JQL filter syntax. It’d help with per-person reports, personal task boards, etc.

If I understand your needs correctly, this is already possible in Fibery.

With the Quick Filter feature, you can turn this filter into a Quick filter button on the view.

[kalman]

Teaser from Quick Filters: It may seem that this is not related to quick filters, but we are doing it iteratively. First, we make it possible to disable existing filters and filter groups in the filter pop-up. The next step is to bring the filters to the Quick Filter Bar.

Stay tuned!

[carson]

I’ve read the spec and this thread: it all looks great to me! Useful feature, good UX implementation, edge cases handled using sensible rules/defaults.

It’s awesome that you guys post your design specs. Thank you!