Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Create a JQL Query for Component owner

We have a somewhat unique project with hundreds of Components. What one of my agents would like is the ability to create a filter that just searches for her issues by the "Component Owner". The idea is that once it's updated in components (with the proper owner) her filter would dynamically update without her having to adjust the filter to add her new components (as shes the owner of a few new ones every week). I'm fairly certain there isn't a solution to this, but also enjoy very much proving her wrong, so can someone please confirm this?

2 answers

1 accepted

2 votes
Answer accepted

There's a function called componentLeadByUser that would do the trick, and it's in the default JIRA functions.

Sorry for proving you wrong smile

CURSE YOU NIC

But thanks

Wait, still getting problems. I am using: componentsLeadByUser(usernameinhere) but am getting "Error in the JQL Query: Expecting operator but got '('. The valid operators are '=', '!=', '<', '>', '<=', '>=', '~', '!~', 'IN', 'NOT IN', 'IS' and 'IS NOT'. (line 1, character 21)" I also tried componentsLeadByUser = username and got Field 'componentsLeadByUser' does not exist or you do not have permission to view it.

no, the way you use it is "component in componentsLeadByUser(username)". Like in the example in the doc. Burn!

I recently opened a suggestion to remove this limitation. Please vote for it if you agree it would add value to allow currentUser() to be the parameter of this function.

https://jira.atlassian.com/browse/CLOUD-11168

@Nicolas Bourdages 

Would you you be able to help me figure out why the issues were found when i did component in componentsLeadByUser(username)?

I've put the user's username but nothing...

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you