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

Including Component Lead in Issue filter

We would like to be able to include the component lead in our issue filters. We have 6 Service Leads (product managers) who need to be able to see all issues related to their components (services). 

Can component lead be included in an Issue filter?

3 answers

1 accepted

0 votes
Answer accepted
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Dec 03, 2019

Hi Shannon,

I'm unclear why you cannot achieve your goal by simply using the Component itself. You could create a filter for each product manager based upon component. You could further associate these filters to a Dashboard for each PM.

There is not a field for component lead that could be leveraged w/in a JQL.

Thanks Jack. I wonder if there is an enhancement request for this that I can vote for or if I should submit one. 

We are able to use " componentsLeadByUser() " to filter results for a user so they only see issues for their components, but we end up losing the value of cross functional engagement should someone be absent. They'd have to create an ad hoc filter to include componentsLeadByUser() naming the absent lead in order to see their issues. 

I recently ran into this limitation, and opened a suggestion you can vote for (please do, since I REALLY want this improvement to see traction).

Thanks. I also find this annoying. As there are many components per lead and it's annoying to list all components in JQL - would be so useful to add component lead into a quick filter.

@Carmen Valdés Téllez 

Thanks a lot for the tip! It works fine and suits with what I needed!



You can use the function componentSleadByUser (), for example something like this project = PROJECT AND component in componentsLeadByUser(),  With this the fiter shows your issues assigned for you as component lead, if you want to see from an specific one, you hace to put the user in the beckets: project = PROJECT AND component in componentsLeadByUser(USER). I hope it helps

I just tested this, and the case of a specific user is difficult because you need to use the username of the user and that's not easy to find (IMO) except by trial and error.

Regardless, I'm not sure why this seems to be working now but not when these tickets were opened. I am now able to create a Quick Filter for "My Components" that shows the current user all "their" issues based on component ownership.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events