I also would like this feature in.

But just to head off any further discussion about the above, you can't file a complaint against a company because they don't want to add a feature.  It's like filing a complaint against a grocery store because they don't have unsalted butter.

That said, hopefully Atlassian will listen to its power users.

To Martin, Clement, and Raymound,

If Atlassian refuses to fix this issue then I recommend you report Atlassian to the U.S Better Business Bureau *http://www.bbb.org*

File a complaint against Atlassian, This will cause the company to have a mark against them and US companies will avoid doing business with them.

I have already provided Atlassian with all the information they need to implement this search. It would only require 1 additional database table and the macro already exists in Jira.

@James Allen, thanks for your humble and wise words

and for creating the issue JRA-62780 based on my (obvious) last comments.

I was about to do the same but I voted for your JRA-62780 instead.

Everybody, please vote for the JRA-62780 !

We are all aware of the tickets status that is why many people are commenting on this issue yesterday!

@Otaviano Neto You are stating the obvious again not helping anybody.

@James Allen, sorry for trying to help you...

As you requested Atlassian to assign *a *resolved ticket to someone (expecting any resolution action), I thought you had not noticed that it was set to "resolved as won´t fix".

@Otaviano Neto I already am aware of this, Why are you stating the Obvious?
@Otaviano Neto Read The Entire Thread Before Commenting!

Atlassian you need to use Jira properly, an unassigned ticket brings no action!

Jason Freund, this ticket is unassigned. Atlassian does not care
I already gave everyone one method to search comments! Did you not read it?
Atlassian you need to use Jira properly, an unassigned ticket brings no action!

Please re-open

+1 I've always wanted this feature. Not to find bugs that I have commented on, but to find bugs that other engineers have commented on.

+1 please make this a JIRA feature

You can view JIRA Comment Toolbox . To search on author of the comments with or without date range.
https://marketplace.atlassian.com/plugins/com.kostebekteknoloji.plugins.jira.jira-comment-toolbox
Moreover, you can use JIRA Comment Toolbox for these;

• Custom Comment Fields,
• Custom JQL function
• Delete issue comment
• Delete user all comment
• Update author of the comments.

I have a user who has been renamed, cant find his comments so I can delete him.

Any explanation why you won't implement this? Is it really harder than the other thousands of features which have been implemented?

I'd like to add that it would be nice to search for issue not only current user has commented on but issues where comments were added to by anybody since X time ago.

RIP

Concerning votes, this issue is on position 100 of over 35,000 issues, so there seems to be quite some need, and for end users like me, none of the mentioned workarounds works: The "autowatch" preference does not trigger the search to return only issues I commented on, same applies for issueHistory() function (which is anyway too limited with only 50 issues). I can't add this very basic functionality via add-on because of lacking rights, and for the same reason, I can't even see whether any of the mentioned add-ons is installed (according to search in documentation) - is any of them active in this Jira installation?

Is it really so much work to implement?

Yes, very disappointing indeed. This seems to be such a basic feature missing for a sophisticated issue management system.

Very disappointing, but better to know that it will not be implemented so thanks for that information.

Hello Felipe Somolinos - I can help you,
Here is my solution to your comment delete issue.
You have a developer who commented once or twice in a huge jira project, Howto find his changes???
Fix: Goto the users profile page-- >Look for the Users Activity Stream <---

In the Users Activity Stream it shows every ticket change and every ticket comment for that user.

Atlassian just needs to simply convert the macro for user history stream into a searchable filter, shouldnt be difficult to fix.

Felipe Somolinos - Goto a Users Profile Page, Next Goto User Activity Stream

This is not an actual fix to the issue because activity stream is not 100% accurate and the comments need better tracking in the main java of Jira

Hi, felipe19

I believe it should be possible with my Add-On https://marketplace.atlassian.com/plugins/jql-pro

And yes, I agree that this is strange that such obvious functionality is missing in the native JIRA functions.

If you need my help with such query - feel free to contact me vitaliy.zurian@gmail.com

Cheers!

+1

Hi, I really just want to find out which is some comment from an specific user. It can be for inumerous reasons.

In my actual issue, I have a developer that worked with us for a couple of days, made a comment somewhere in a huge project with hundreds of issues and comments, and I can't just find out what he commented to realize if it is something reasonable that I would like to keep or not. Right now, its just bugging the users database.

It could obviously be used for thousands of filters, like we have de assignee filter. But if I want to check all the comments made by an user for a period of time? I'm not able to do that. If I want to track back all the comments of some stakeholder that misunderstood something and want to read all the comments and the interactions between this stakeholder and the team? How can I track this?

Finally... There are a lot of reasons and filters that can be made by the simple implementation of the "commented by", or something similar, variable.

Thx.

FG

+1

Agree with the commenter on 11 years and counting to get this implemented.

Mark,

I see another very useful function: If you are a big company with a turnover and you are in a small field (say, X-ray physics) and emails are based on names like staffan.ohlsson@esrf.fr, you would really like to delete instead of disable.
If you disable and that person comes back after having been at another facility for a few years, you do not want the returnee to have "Your account has been disabled, sorry" as a reply to his service request when he asks for an installation of his new computer.

To avoid that hassle for a returnee might be worth deleting some comments on a ticket 2 years old.

Staffan

C'mon guys! It will solve tons of problems hunting comments that get the "Delete" function stuck!

I assume you are referring to the fact that you can't delete a user who has made comments, and so you want to delete such comments in order to allow you to delete the user?

But why would you want to delete a user who has made comments?
Would it not be easier to just disable the user and keep the comments, which are presumably interesting and part of the true historical record?

The only legitimate use case that springs to mind is if you have a public JIRA ... and some user came along and added spam comments.
But in that case, I would think that some specific spam killer functionality might be preferred.
There could be 1000s of such comments - you don't want to delete these by hand, you want to be able to just go "delete all comments made by user X".

C'mon guys! It will solve tons of problems hunting comments that get the "Delete" function stuck!

I love the edit...

This sounds like such a core requirement... mind blowing it takes 11+ years to implement a one hour feature

For JIRA Cloud you could use this JQL Pro Add-On

Among few functions, it can find issues for which a user has left a comment - by the user email.

But this does require the Script Runner plugin to be installed. The version page from Atlassian is currently broken, so I can not check, whether this plugin is available in JIRA 5.2 compatible version.

Your last suggestion does appear to give us what we need, ty

issuefunction in commented("by mmonaghan") ORDER BY updated DESC

Yeah, sorry about that.
I spoke with a colleague and he suggested:

"issuefunction in commented("by mmonaghan") ORDER BY updated DESC"

This certainly catches bugs on which I've commented - and - including those which have no comment containing the text 'mmonaghan'.

Maybe give that a whirl, and see if it catches what you need.

I tried this in JIRA 6.2:

comment ~ currentuser() order by updated DESC 

I found what others have reported... the query returns issues where my name is mentioned in a comment, not issues that I have commented on.

Mick, if I understand you correctly you would search in this Atlassian Instance:

comment ~ "Mick Monaghan" order by updated DESC ?

It does not work for me in our own JIRA 5.2 instance. It will find comments only, if my name is as such in the comment. But this is not what I and others here are waiting for.

I'm on Jira 5.2, and can use this JQL statement to get the list of bugs I've commented on:

comment ~ myusername ORDER BY updated DESC

Is the reason that this has been open for over 10 years that it is complicated to implement or just that it isn't a priority?

Please please Atlassian, this is really essential. We are using OnDemand and are limited for some of the suggested workarounds, core product support would be the best approach.

Atlassian Where are you with fixing this issue?

I tested 6.1.4 JIRA and search by comment does not actually work.
Inaccurate results, Search system is loose,
THIS IS STILL A BUG
Search by Comment has never been fixed.
Yes you can try and search for a user with comments, but the results are not accurate

i got what i needed - when you sort by the new adv custom field - the field name "cf[10801]" becomes visible in the JQL, from there i just added: cf[10801] != "Raffi"

project = ProjectKey AND (status = Open OR status = reOpened) AND updatedDate < -4w AND cf[10801] != "Raffi" ORDER BY cf[10801] ASC, key DESC, updated ASC, priority DESC

i could be wrong but a customer field (advanced) labeled as follows may be the solution.
now if i can filter using JQL by the same field, then i am there.

the field is:
Username of last updater or commenter
Display the username of either the last updater or commenter
depending on which happened most recently.

I agree. I wrote a plugin that provided a custom field that was set to True if the last commenter was not the assignee with this idea. The trouble is that adding a new comment to an issue doesn't trigger the index update for the issue. So I seem to recall that the search wasn't as useful as I wanted. Still, I used it to color cards in GreenHopper Kanban boards to give me a clue about what to work on next. In the end, searching on Updated in Last Day, Updated in Last Three Days worked just about as well

TY @Chris
this helps isolate the neglected tickets.
still would be great to identify the tickets that i own an update on.

thanks again.

@Raffi

I had occasion to build a similar search. I just looked for issues which hadn't been updated for more than 1 week. Here's the query:

resolution = Unresolved and updatedDate < -1w

You can adjust updatedDate to suit your tolerance.

not sure if this is already covered...

i am trying to identify tickets that are status = Open that i was not the last person comment on.

the ability to identify tickets with status = Open that "i" (or any user) was not the last person to comment on will be very helpful for catching up on overlooked tickets.

patrick10
OnDemand includes the Toolkit plugin

What can I do when using on-demand and cannot add these plugins...

Solution is to install Script Runner plugin (https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner/version/1017) and then use for searching issueFunction custom field.

https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+JQL+Functions
Example from this page:

Find issues commented by jbloggs within the last 4 weeks:

We also find such an ability useful and would like to see it implemented.

+1

Using the "Participants" field (as part of the Jira Toolkit plugin) is a decent work-around, but having a direct search supported by the core Jira product would be more intuitive and would not require a plugin. In my view, the need to search all issues on which I've commented is as common as searching all issues on which I've voted or am watching.

Via http://stackoverflow.com/questions/2145913/jira-how-to-find-issues-that-at-some-point-has-been-assigned-to-you I found https://studio.plugins.atlassian.com/wiki/display/JTOOL/JIRA+Toolkit+Plugin

The toolkit is a set of neat custom fields Atlassian developed for their own use, among others, it adds a calculated particpants custom field

The HP/Palm Jira Search Plugin has a JQL function that enables searching of comment author and date in addition to comment content. The plugin also has a visual editor that assists in filling out the parameters and is a generic visual editor for all JQL.
The JQL for a comment search can then be

issue in hasComment("really bad bug jira", "jane zhang", "", -4w, "") 

The plugin is free

J-Tricks Plugin might solve this with commentedByUser([User]) (but it is commercial)

@Scott: Might be good if someone can check Lauris #1 comment "Duplicates with JRA-1187". One is an improvement, the other one a new Feature issue... keep one, close the other one. Thanks

We too need something similar. We need to generate a filter for all issues where a user has logged work in the last week regardless of if that issue is currently assigned to them or not. Something like, "workee = currentUser() and updated >= -2w". A similar filter on updated issues might also work, "updatee = currentUser() and updated >= -2w".

Perhaps a plugin like, "Jira Timesheet Report and Portlet Plugin", will get us what we need. I'll try to report back with our success.

I would like to see this implemented as well but with an additional twist. We have users who create a large number of issues but due to email overload, they don't pay attention when an issue has been commented on. They would like to search based on the comment author when the author is not themselves.

This is such a great need for us: we really need it to aid timetracking.

I would like to be able to pull up a report of all issues I have commented on in a given time period (usually, one day).

We do use the participants field and can pull back all issues where one is a participant, updated within a certain time period, but just because someone updated the issue, it doesn't mean that all participants were active on that issue in that given time period.

I'd like to see a list of all my comments for the day (or week, or month). It doesn't seem like it ought to be that hard to add - any plans to add this feature?

Sergiy,

You are correct, we do not provide an ability to search for date ranges on comments through JQL. You can search for issues you have commented on, which have been 'updated' in a certain time, which is close, but not exactly what you are after.

Unfortunately JIRA 4.0 with advanced JQL does not address this issue.
From my side I would extend this request with more general - issues affected by me,
that is what I asked in JIRA Support, answer was negatige -

Please give us a sample of JQL query returning the following - list of issues updated (created, edited, commented, etc.) by specific user over defined date range.