Can users that have been mentioned in issues be queried by JQL?

[Jacques]

Since the latest 5.1.3 JIRA upgrade the @mention utility has been improved considerably.

I would like to know if there exists any JQL instruction to query in which issues I (or any other user) was specifically "mentioned"?

[Christian Reichert]

Hi Jaques,

it does work with JQL - here for example is a JQL which I use to provide Users with a list of Issues where they have been mentioned during the last 7 days:

(summary ~ currentUser() OR description ~ currentUser() OR comment ~ currentUser()) and updatedDate >= -7d

[Jacques]

Thanks Christian!

This does indeed do the job!!

[Sven Wenzel]

• (summary ~ "username" OR description ~ "username"  OR comment ~ "username") and updatedDate >= -7d

[Joel Edwards]

Very helpful, thanks!

[Johan Persson]

The statement from OP can never work since neither currentUser() nor currentLogin() support the text search operator "~".

The text search can only be made with literals. Cannot really understand the technical reason behind this limitation though.

See currentUser()

[John Gooch]

strange, I just ran it and it worked as expected. Perhaps it behaves differently based on your Jira installation. 

[Sid]

This looks for the user name in the whole comment section. I definitely would NOT want the issues that I commented, I only want the issues that I am mentioned on. So this would not be an ideal solution. @Johan Persson is right. 

[NancyB455]

I did not find that to be true.  This query comment ~ currentUser() ORDER BY created DESC only found where I had been mentioned with an @ sign, not when I had created a comment. (JIRA Server, 7.13.1)

[Mudi Dissanayake]

doesn't work for me. comment ~ currentUser() doesn't find the issue I'm mentioned on. 

but comment ~ "hello" finds it.

[Amy Basque]

Mentions created in the new issue view will not be found in queries. Please vote for this issue! 

https://jira.atlassian.com/browse/JRACLOUD-72207

[Mudi Dissanayake]

Thanks, silly question. how do I vote for that, where the vote link ?

[Amy Basque]

Not silly at all! On the right hand side under the reporter, click This affects my team. I took a screenshot for you, but attaching it isn't working. 

[Jowin Zachariah]

So, I struggled with this myself quite a bit and none of the above answers worked out for me. The only workaround I found is hardcoding the id of the user (sigh!, why Jira?) and then using jql like this : 

comment ~ 551000:10eea9db-900e-4000-9bf0-f9000ceee7d5 AND updatedDate >= -7d AND status not in ("Done")

In chrome : 

To get this id, right-click on a comment where the user is tagged and click inspect element.

You will see a <p> tag and if you expand that you should have one of the <span> tags with data-mention-id of the user you want to search for.

[Jasmyn Han]

This worked great for me

[Marek Jasiulewicz]

great tip thanks 

[Jolie Huang]

data-mention-id works! Thank you so much!

Both currentUser() and username didn't work for me. 

[Nazar Konevych]

this is exactly what I was searching for. Works as a charm

[Simon WYCKAERT]

Very helpful, worked for me. Thank you!

[Joana Correia]

HI all, anyone knows how I could query the tickets where i was mentioned on the last comment of the ticket?

thanks!!

[Sheila Ottersen]

I also need this feature

[Katie Thebeau]

How do I change current user to another user in the system for this: 

• (summary ~ currentUser() OR description ~ currentUser() OR comment ~ currentUser()) and updatedDate >= -7d

Not sure why I am having such a hard time! 

[Robert Wójcik]

Username = katiethebeau

(summary ~ katiethebeau OR description ~ katiethebeau OR comment ~ katiethebeau) and updatedDate >= -7d

[hudziakp]

You can use this plugin: https://marketplace.atlassian.com/apps/1222753/user-mentioned-jql 
but it will show only those ticket where comments/descriptions were created after installation.

[Trilok Singh Vinjrawat]

I am looking for a JQL that can show the issues where the current user was mentioned in comments that were made in the last 7 days. 

[NancyB455]

Hmm, interesting.  Setting aside the user mention for a moment, is it possible to query for issues that have been commented on in the last 7 days (and not updated in any other way?)  

[Jacques]

hi Mirek,

thanks for mentioning this, but I knew this already :)

I just thought that if they add this cool feature that there should be a way to filter for issues where you've been mentioned as they might be issues where you're none of the regular roles (assignee, reporter, watcher,...) that already exist and for which you can filter.

I found this issue talking about this feature: https://jira.atlassian.com/browse/JRA-27594 and as mentioned there (I've also tried in my environment) filtering for @mentions doesn't work.

Let's wait if some more people vote on the forementioned issue to get it implemented.

regards,

Jacques.

[Nancy Bonanno]

If you have access to issuefunction, then issuefunction in commented("by userID after/before yyyy/mm/dd") works well.

[Ana Bolanos]

This one works for us.

(details ~ currentuser() OR comment ~ currentUser()) AND updated >= -7d AND status not in (closed)

HOWEVER, it is for the current user. I want to see a specific person that was mentioned as he will be OOO. I think in a comment above someone alluded to that this cannot be done.

[Ana Bolanos]

I found it!

This use case is to cover for someone that is OOO, so the fact that it captures the comments it creates is not an issue. 

(comment ~ mmouse OR details ~ mmouse) AND updated >= -1d AND status != Closed

and as someone mentioned, go to this ticket and vote for it. 

https://jira.atlassian.com/browse/JRASERVER-27594

[Trilok Singh Vinjrawat]

One thing I have noticed with this JQL is that, if the current user was mentioned in a Jira Issue months ago and the issue was updated without the currentuser mentioned in the past 7 days the JQL still returns that Jira Issue.

[Anthony Brittis]

I know this is an old question, but I just ran this JQL and noticed that it only returns issues where currentUser() is mentioned in the LAST comment.  It didn't locate issues where currentUser() was mentioned in other comments besides the last one.  

Has anyone else seen this behavior?

Anthony

[Amy Basque]

I haven't seen that, but this filter is not working quite right for me. It is not showing all tickets that a user is mentioned in. I can't figure out what's different about the tickets that are showing up compared to the ones that are missing (they're in the same project, same workflow status, same issue type, etc.). 

[Ernesto Ruy Sanchez]

I'm using JIRA OnDemand (6.2 as of right now I think?).. and this does not work as I expected

I expect to get a list of issues where I have been mentioned using @ + myname

However, I do get a list of issues where my name has been mentioned as text in a comment, but not as an actual @mention

Anyone having this same problem?' What is the JQL query for this?'

I tried the JQL: comment ~ currentUser()

[Andreas Vallberg]

In Jira On Demand, this worked for me. I guess it is case sensitive.

project = ABCD AND comment ~ CurrentUser()  ORDER BY created 

[Stuart Dalrymple]

Hi all,

I am using the following JQL to create a filter on @mentions:

comment ~ currentUser() and updatedDate >= -30d

It works, however, when I've gone and deleted the comments I was mentioned in (they were for testing the filter) - they still show up in the search! Is the JQL searching the history and not the comments that actually exist? Is there another JQL that will only display the items I'm still actively mentioned in?

[Mirek]

Hi Jacques,

As I know mentioning is only used to share the issue with other users (the same behavior like using Share button) and send a notification. It is not possible to achieve a search who was mentioned in a particular issue.

You can only search for issues that a particular user is watching or voting using:

* watcher

* voter

like for example..

watcher = someone, watcher = currentUser()

If you want that kind of feature you can create a new request. For more information about how Atlassian implement New Features, please see the Implementation of New Features Policy.

I hope that will help

Regards,

Mirek