-
Suggestion
-
Resolution: Won't Fix
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Hi everyone,
Thank you for your feedback and votes; however, we have decided to close this issue. As you can see from the history, this issue has been open for almost 12 years, yet I do not expect it to be on the JIRA team's roadmap in the foreseeable future. It is unlikely we will resolve it as described in the original request.
The easiest way to view issues that you have looked at recently is to use the issueHistory() function. This is easily accessible by clicking "More..." under the "Recent Issues" section of the Issues menu.
If you find yourself needing to frequently track issues you have commented on, we recommend enabling the "autowatch" preference.
Alternatively, this function has been implemented in a number of JIRA add-ons:
As is the case with all issues on jira.atlassian.com, closing this issue does not mean this functionality will never be a part of JIRA by default. However, the JIRA product management team is making an effort to make jira.atlassian.com a more valuable tracking tool by closing the issues that we do not expect to work on in the reasonably foreseeable future.
As always, please do not hesitate to contact me directly with questions.
Regards,
Dave Meyer
JIRA Product Manager
Original request description:
Hi,
Our users would like to search on issues he has added comments to. It would be a handy way to choose issues to be watched.
We can currently search on text within comments, but not filter on comment-authors.
In the filter page, perhaps as one of the attribute fields, there could be a field for "Includes Comment By".
Thanks,
Steve
------------------------------------------------------------------------
Stephen Butler, Software Logistics Dept.
SOLINET GmbH Solutions for Innovative Networks
Mittlerer Pfad 26, 70499 Stuttgart, Germany
Tel +49 711 1398 1357, Fax +49 711 866 1240
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
- is related to
-
- Closed
- relates to
-
JRASERVER-34718 Not possible to delete user with comments
-
- Gathering Impact
-
-
- Closed
-
- Closed
- was cloned as
-
- Gathering Interest
[JRASERVER-1648] Allow search on issues I have commented
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.
Otaviano Neto
added a comment - @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 !
Otaviano Neto
added a comment - @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.
Otaviano Neto
added a comment - @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
added a comment - @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!
Otaviano Neto
added a comment - @James Allen, in fact they changed the issue status to 'resolved' with the resolution type "Won't fix" on 06/Feb/2015.
See the comments at the Description field:
{quote}
[...] we have decided to close this issue. As you can see from the history, this issue has been open for almost 12 years, yet I do not expect it to be on the JIRA team's roadmap in the foreseeable future. It is unlikely we will resolve it as described in the original request. [...]
{quote}
Very disappointing...
Otaviano Neto
added a comment - @James Allen, in fact they changed the issue status to 'resolved' with the resolution type "Won't fix" on 06/Feb/2015.
See the comments at the Description field:
{quote}
[...] we have decided to close this issue. As you can see from the history, this issue has been open for almost 12 years, yet I do not expect it to be on the JIRA team's roadmap in the foreseeable future. It is unlikely we will resolve it as described in the original request. [...]
{quote}
Very disappointing... 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.
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.