www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tony Stevenson (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (INFRA-10138) Consider enabling the participants field for JIRA
Date Tue, 01 Sep 2015 08:10:45 GMT

     [ https://issues.apache.org/jira/browse/INFRA-10138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Tony Stevenson closed INFRA-10138.
    Resolution: Won't Fix


Sorry but we are not willing to add new features to JIRA at the moment. Whether that be an
add-on etc.  

This is primarily because our JIRA instance is massive, and many plugins behave poorly and
want to index all issues etc - which can make using said plugins more friendly for the end
user.  However when you have 10 modules all doing the same thing, and not doing it nicely
(or sharing indexes) it can cripple JIRA.

> Consider enabling the participants field for JIRA
> -------------------------------------------------
>                 Key: INFRA-10138
>                 URL: https://issues.apache.org/jira/browse/INFRA-10138
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: JIRA
>            Reporter: Jonathan Eagles
> Currently there is no way (without access to the underlying database and using SQL) to
query comments by user.
> Sadly this is not natively supported by JIRA.
> [JRA-1648] Allow search on issues I have commented - Atlassian JIRA
> Work around discussion here
> http://stackoverflow.com/questions/5975529/issues-commented-by-me-in-jira
> You can get close approximation by looking at the watchers list since when you comment
you are auto-added.
> However, if we enable to participants fields than it can be done using the issuefunction
> https://issues.apache.org/jira/issues/?jql=issuefunction%20in%20commented%28%22by%20jeagles%20after%20-2w%22%29

This message was sent by Atlassian JIRA

View raw message