Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Filter for Kanbanboard to view all issues with a specific label in the epic

I want to create a filter for Filter for Kanbanboard to view all issues with a specific label in the epic

1 answer

1 vote
Mark Segall Community Leader Dec 07, 2022

Hi @David Verbeure - Are you saying that you want something where it simultaneously filters a single epic and all issues with a specific label within that epic?  You could do something like this:

"Epic Link" = ABC-123 AND labels IN (YOURLABEL)

No, I want to create a filter for the kanban board in which I see all tasks from epics with a specific label

another possibility would be to copy the labels from epics to the child tasks.
but how do i do this?

Like Mark Segall likes this
Mark Segall Community Leader Dec 08, 2022

Yes - Sadly, you won't be able to perform a double query like that where you're looking for epics with label x followed up by all of their respective children.  However, your alternative may work theoretically with some Jira Automation. 

  • TRIGGER: Field Value Changed (Epic Link)
  • ACTION: Edit Issue (Labels)
    • {{issue.Epic Link.Labels}}

Note - I could not get this to work in the server environment I have available to me.  I ran into a couple issues

  1. It didn't accept the above as a smart value because of the space in Epic Link.  Instead I had to use {{issue.customfield_xxxxx.labels}}
  2. Failed when the Epic had more than one label as it tried to read the multiple values as literal and failed because it would come across as "label1, label2" which contains a space. 

Not all flavors of server are the same so this may work for you, but if it doesn't, hopefully my notes help explain why.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events