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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,560,276
Community Members
 
Community Events
185
Community Groups

reporter ≠ assignee

Pavel Lyko
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 16, 2023

Hello
how to write a query that limits my search so that it does not display tickets where the submitter is also the resolver?
something like
reporter ≠ assignee

1 answer

1 vote
Aron Gombas _Midori_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 16, 2023

You can't use two fields on the two sides of the "!=" (not equal) operator, unfortunately.

You can only compare the "reporter" against a user literal or a JQL function:

reporter != joe

reporter != currentUser()
Pavel Lyko
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 16, 2023 • edited

Thanks, but unfortunately it's not enough.
I have a filter whose result displays tasks from department of 25 people.
So the resoult would be displayed OK only for "current user", but to all other it wouldnt...

Aron Gombas _Midori_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 16, 2023

Yes, I understand the problem, I'm just saying that it cannot be solved in plain JQL. 

A potential workaround could be:

  1. Export the data to Excel, containing these columns:
    1. issue key
    2. reporter
    3. assignee
  2. Add a formula to the fourth column which returns true if the reporter column is not equal to the assignee column.
  3. Filter your spreadsheet to those rows where the formula evaluates to TRUE.

Now you have the key of the corresponding issue, voila!

jira-issues-selected-fields.png

Suggest an answer

Log in or Sign up to answer