Skip to content

Add support for assignee wildcard for graphql boards [RUN AS-IF-FOSS]

euko requested to merge 280781-support-assignee-wildcard-filtering-boards-frontend into master

What does this MR do?

  • Adds support for filtering by assignee ANY or NONE for graphql-based boards and partially resolves #280781 (closed).

What was broken and what's a graphql-based boards?

We have supported this particular filter, assignee wildcard for the classic boards (the one in production). However, for graphql-based boards such as epic swimlanes (group and project boards use GraphQL behind a FF :graphql_board_lists), the feature didn't work because we didn't have the support in GraphQL. The GraphQL support got merged in !58996 (merged).

For example, selecting assignee = NONE should make the boards to display only the issues without any assignees:

Filter working in classic boards in production Filter not working for graphql-based boards like epic swimlanes
Screen_Recording_2021-04-14_at_3.52.29_PM Screen_Recording_2021-04-14_at_4.04.18_PM

Screenshots (strongly suggested)

Using epic swimlanes:

Screen_Recording_2021-04-14_at_4.02.18_PM

You may use both group and project issue boards to test the changes after enabling :graphql_board_lists.

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • Security reports checked/validated by a reviewer from the AppSec team

Related to #280781 (closed)

Edited by euko

Merge request reports