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?
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.
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.
...eturns true if any content is returned for the webResponse.body.data.first s...