Kanban boards quick filters

[Mangali Chandrashekar]

Do we have option to create quick filter for the selected Kanban boards automatically once component created in project area?

[Frédéric Tardieu]

Hi @Mangali Chandrashekar ,

Jira doesn't offer a built-in way to automatically create quick filters when a new component is added: quick filters on Kanban boards must be created manually via Board Settings → Quick Filters, using a JQL expression like component = "Your Component".

A couple of workarounds for the native board:

• Automation for Jira can't create quick filters directly (they're not exposed in the automation API), but you could set up a rule that notifies a board admin when a component is created, prompting them to add the corresponding filter.
• If you have ScriptRunner or similar, you could script the creation via the REST API (/rest/agile/1.0/board/{boardId}/quickfilter), though this requires maintenance.

If you're looking for a more visual, multi-dimensional approach, I built an app called Board Studio for Jira Cloud that lets you use components (and any other Jira field) as swimlane dimensions dynamically — no manual filter setup needed. When you add a component in your projects, it's automatically available as a grouping/filtering axis on the board.

In addition, activating auto-refresh feature will have your Kanban updated as soon as a new component is associated to a work-item part of your filter.

Here's how it would look like in Board Studio app, with a filter as data source input, a Status field horizontal swim lane and grouping by Components Jira field:

With some Components groups expanded to see work items inside (just double-click on a group to expand/collapse it):

With all Components groups expanded:

Disclosure: I'm the developer of Board Studio.

[Martin Runge]

Hi @Mangali Chandrashekar

Before diving into complex automation, consider whether a Dynamic Quick Filter meets the need. Instead of creating a new filter for every component, you can create one or two filters that cover the most frequent use cases.

The quick answer is no; Jira doesn't have a built-in "toggle" feature that automatically generates a board filter whenever a new component is added. However, you could address this by using Jira Automation with the Trigger: Component created and Action: Send a Webhook (to the Jira API) to add a new Quick Filter to the specific Kanban Board.

Note: This requires an API Token, replacing URL & {boardId} in the endpoint URL, and "Board Admin" permissions for the user executing the automation. It’s a bit technical, but it’s the only way to achieve true automation for board configuration.

1. Go to Project Settings > Automation.

2. Trigger: Component created.

3. Action: Send web request.

4. Endpoint: https://{your-domain.atlassian.net}/rest/agile/1.0/board/{boardId}/quickfilter

5. Payload (JSON):

   JSON

   {
     "name": "{{component.name}}",
     "description": "Automatically created filter for {{component.name}}",
     "jql": "component = '{{component.name}}'"
   }
   

[Bill Sheboy]

Hi @Martin Runge 

As a reminder, when posting bot / AI-generated content, please ensure you disclose the sources as required by the community guidelines:

https://community.atlassian.com/forums/custom/page/page-id/rules-of-engagement

Regarding your automation rule suggestion, that will not work...and some of the suggestion aspects were likely hallucinated by the source bot / AI-tool:

• There is no Component Created trigger. There is a Compass Component Created trigger.
  • https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Component-created-in-Compass
• There is no public REST API endpoint to create a quick filter for a board
  • https://developer.atlassian.com/cloud/jira/software/rest/api-group-board/#api-group-board
  • There have been multiple ecosystem suggestions over the years to add that feature, such as this one:
    • https://ecosystem.atlassian.net/browse/ACJIRA-2465
  • If one tests the recommendation from that AI-guess, one would observe the error that the PUT and POST methods are not supported for the endpoint

Kind regards,
Bill