Add ability to negate selected filters for a board

Problem to solve

Is there a way to add a board filter as a negation of the selected filter?

Further details

I'd like to create a board that allows me to exclude certain items via negated filter options

Proposal

Add a way to negate any desired selected filter

What does success look like, and how can we measure that?

I can create a board that shows all excpt a given milestone, user, label, etc.

Links / references

changed the description

Zendesk: https://gitlab.zendesk.com/agent/tickets/102743 (internal-only link)

This is probably mostly addressed by https://gitlab.com/gitlab-org/gitlab-ce/issues/27747. The difference for this request would be that the customer also wants the ability to save the filter and have a board based on it always available.

added Plan [DEPRECATED] boards customer ~2975006 frontend labels

/cc @victorwu

I would like to be able to show all issues not created by me.

mentioned in issue #10619 (closed)

changed milestone to %Backlog

added [deprecated] Accepting merge requests label

Isn't it related to !1770 (merged)?

added devopsplan label

added groupproject management label

added Enterprise Edition label

Hi!
It seems that https://gitlab.com/gitlab-org/gitlab-ce/issues/27747 did not include the ability to exclude objects from the filters. Is it still a feature that can be promoted for implementation?
I can see great benefits in the day-to-day life when using boards views with our teams, and it could be also very useful on the list views when bookmarking particular queries.
Thanks for letting know if there is any plan for it!

This feature would be useful when using group-level boards. We try to keep all our labels at the top-level group to reduce the amount of label administration that goes on between the subgroups/projects. We have multiple boards that share a common set of state:: labels to track the progress of the issues... this causes issues to appear across multiple boards. We worked around this by adding a set board:: labels to filter issues by board which adds unnecessary overhead to the boards and issues. This has its own set of complications as well since we now have to change labels to get the issues to show up on a different board then it was already on.

If we could exclude a set of labels from a board then it would allow us to remove and maintain our board:: labels.

Looks like a lot of good discussions happened on gitlab-foss#21747 (closed) under the additional changes section on this topic.

added sectiondev label

Is there any plan to add this feature? We are in the process of evaluating whether we can use Gitlab issue tracking in place of Pivotal, and as I'm creating boards, this feels like a crucial feature.

GitLab Premium customer is interested in this feature (ZD link, internal only)

added Category:Team Planning label

A US PubSec customer expressed interest in a resolution to this issue: https://gitlab.my.salesforce.com/0064M00000ZsJQ6.

It seems extremely weird that this feature is not available.

We can set negating filters in the board's search bar, but we can't set negating filters in the board settings? That is a huge shortcoming.

@EmDeen completely agree. Our tentative plan is to replace the current board scoping experience with the filter bar and make it a "saved query" as part of this initiative -- &5516. My team is not the DRI for this work stream, so I can't speak to timelines here.

FYI @mushakov @cdybenko

removed Plan [DEPRECATED] label

added groupproduct planning label and removed groupproject management label

• 4,000 user GitLab Ultimate customer is highly interested in this feature (internal link). customer priority6
• Why interested: This team heavily uses boards to triage and plan work - having this feature will help them more easily plan/track work on boards.
• Current solution for this problem: Not aware of one currently, please feel free to share if you have a workaround.
• Impact to the customer of not having this: As this customer adopts GitLab Plan features, this is creating a bit more friction to adoption efforts.
• Questions: Is there any chance we might be able to pick up this issue in the near term?
• PM to mention: @mushakov

@gweaver Is the work that your team is doing for "NOT" filters also targeting the board view?

cc: @rachel_fuerst

@mushakov I believe so, but @engwan can you kindly confirm ? Thank you!

@gweaver is there a different issue where y'all are tracking this work? Can you link it, please?

@rachel_fuerst we already support negated filters on the Board filter bar via != (is not). Is this request to extend that functionality to the board scope settings or something else?

Yeah, I'm not sure what the exact request here is. We are not actively working on this right now for the board scope.

Yes, definitely need a negated filter != (is not) to be available when setting the Board scope.

For example, I want to have a board that shows only issues that are not labeled as a bug. Not possible currently the way Board scope works... very strange that it isn't supported right now.

removed [deprecated] Accepting merge requests label

I have a GitLab Ultimate Customer interested in this feature request

I the original poster of this, am a GitLab Ultimate subscriber as well

Can we get an update on this? As far as I can tell it has been in the queue for 6+ years. This seems to fall through the cracks every time and I would just like to know if it is ever going to make it into a release.

We are trying to use project templates to be more efficient and we have our template issues showing up in our parent group boards. We need a better way to exclude them besides telling our people to change the = to !=, after they open the board.

The following customer (240 seats Premium trial) is interested in this capability

• Subscription: GitLab Premium
• Product: self-managed
• Why interested: They are filtering issues in issue boards for team planning using the filter "label != xxx" They want to save the queries in the boards
• Problem they are trying to solve: They use issue boards showing the issues assigned to each developer. They want to filter for example only issues with label "scoping" and "in progress". This is not possible as there is no logical connector AND when filtering issues
• Current solution for this problem: use the filter "label != xxx" and bookmark the webpage