You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have 2 custom fields called "Code Review Approvers" and Code Review Approved By". When a workflow reached the "Code Review" status, a few users are selected to be the "Code Review Approvers". As a user approves, their name gets populated in the "Code Review Approved By" field.
I want to create a filter where the currentuser() is in "Code Review Approvers" but not in "COde Review Approved By", which means they have a pending approval.
The JQL I came up with was:
"Code Review Approvers" = currentUser() and "Code Review Approved By" != currentUser().
This, however, is not returning any issues. What am I doing wrong here?
Hi! you need to use "in" and "not in"
__
"Code Review Approvers" in (currentUser()) and "Code Review Approved By" not in (currentUser())
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I tried a small proof of concept, and it seems that the != portion of your query is what is failing. In my test "Test Multi User Field" = currentUser() returns the one issue that I expect, but "Test Multi User Field" != currentUser(), which I expect to return all other issues, returns 0 issues. I unfortunately have no guidance on this issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.