Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-942

List summary of issues by type on the project browser

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      On the Browse Project page, there are lists of open issues By Priority and By Assignee. It would be nice to have a list By Type as well. Often, fixing bugs is considered more important than implementing new features; currently there's no obvious way (other than a custom filter) to list one type without the other.

            [JRASERVER-942] List summary of issues by type on the project browser

            Thanks for taking the time to raise this issue.

            Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.

            I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.

            Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.

            Kind Regards,
            Kerrod Williams
            JIRA Product Management
            kerrod.williams at atlassian dot com

            Kerrod Williams (Inactive) added a comment - Thanks for taking the time to raise this issue. Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts . In part, that means concentrating on those issues that resonate the most with our users. I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue. Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me. Kind Regards, Kerrod Williams JIRA Product Management kerrod.williams at atlassian dot com

            Holger Schimanski added a comment - - edited

            The issue is actually resolved in recent versions of JIRA (I think, it came with JIRA 5.1 as described in JRA-24278). Look at https://jira.atlassian.com/browse/JRA?selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel and you see "Unresolved: By Issue Type" at the bottom of the page.

            Holger Schimanski added a comment - - edited The issue is actually resolved in recent versions of JIRA (I think, it came with JIRA 5.1 as described in JRA-24278 ). Look at https://jira.atlassian.com/browse/JRA?selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel and you see "Unresolved: By Issue Type" at the bottom of the page.

            CC added a comment -

            Hi,
            We are running a brand new Jira 4.4 here.
            Any news on how to make something similar ?

            CC added a comment - Hi, We are running a brand new Jira 4.4 here. Any news on how to make something similar ?

            This is an old request indeed. but still very valid!

            We have many JIRA projects with all kinds of issues types - an issue summary of all issue types is pretty meaningless to us.

            I think the effort to implement this is rather low. I'm thinking of something similar to the GreenHopper "Quick Filters" ... in this case you would be able to (de)select the issues types you are interested in.

            please implement this small but beneficial feature! Thank you.

            rainer mueck added a comment - This is an old request indeed. but still very valid! We have many JIRA projects with all kinds of issues types - an issue summary of all issue types is pretty meaningless to us. I think the effort to implement this is rather low. I'm thinking of something similar to the GreenHopper "Quick Filters" ... in this case you would be able to (de)select the issues types you are interested in. please implement this small but beneficial feature! Thank you.

            Any ideas on how to do this in JIRA 4.2?

            Holger Schimanski added a comment - Any ideas on how to do this in JIRA 4.2?

            Thank you Estelle for posting your fix.

            The absence of this list was really annoying, but I've added your code (with Holger's nowrap amendment), and it worked beautifully.

            Peter Moline added a comment - Thank you Estelle for posting your fix. The absence of this list was really annoying, but I've added your code (with Holger's nowrap amendment), and it worked beautifully.

            Thank you very much for this solution, Estelle! It works very nice (using it with JIRA 3.13 Enterprise).

            I put it between Priority and Assignee. One little thing, I changed. I am using <td valign=top style="white-space: nowrap;"> instead of <td valign=top style=""> to prevent line breaks in the Issue Type name.

            <td valign=top style="white-space: nowrap;">
            <a href="<%= request.getContextPath() %>/secure/IssueNavigator.jspa?reset=true&pid=<webwork:property value="../.." />&type=<webwork:url value="./string('id')" />&resolution=-1"><webwork:property value="/nameTranslation(.)" /></a>
            </td>

            Holger Schimanski added a comment - Thank you very much for this solution, Estelle! It works very nice (using it with JIRA 3.13 Enterprise). I put it between Priority and Assignee. One little thing, I changed. I am using <td valign=top style="white-space: nowrap;"> instead of <td valign=top style=""> to prevent line breaks in the Issue Type name. <td valign=top style="white-space: nowrap;"> <a href="<%= request.getContextPath() %>/secure/IssueNavigator.jspa?reset=true&pid=<webwork:property value="../.." />&type=<webwork:url value="./string('id')" />&resolution=-1"><webwork:property value="/nameTranslation(.)" /></a> </td>

            Hi Chris,

            I have found that Sam's instruction on Confluence was very helpful but I had to add a little bit more to make it work. The following is the modified instruction that I followed. Also, I have attached files at http://forums.atlassian.com/thread.jspa?messageID=257231490&#257231490 .

            1. Edit $JIRA_HOME\atlassian-jira\includes\panels\browser\openissues.jsp

            Add the following code before the breakdown by priority:

            -----------------------------------------------------------------------------

            <%-- Breakdown by Issue Type --%>
            <b><webwork:text name=" By Issue Type " /></b><br>

            <table cellpadding=2 cellspacing=0 border=0 width=90% align=center>
            <webwork:property value="@StatAccessor/allFilterBy('issuetype')">
            <webwork:iterator value="./keySet">
            <tr>
            <td valign=top width="1%">
            <a href="<%= request.getContextPath() %>/secure/IssueNavigator.jspa?reset=true&pid=<webwork:property value="../.." />&type=<webwork:url value="./string('id')" />&resolution=-1">
            <webwork:component name="

            {./string('name')}

            " template="constanticon.jsp">
            <webwork:param name="'contextPath'"><%= request.getContextPath() %></webwork:param>
            <webwork:param name="'iconurl'" value="./string('iconurl')" />
            <webwork:param name="'title'"><webwork:property value="./string('name')" escape="false"/></webwork:param>
            </webwork:component>
            </a>
            </td>
            <td valign=top>
            <a href="<%= request.getContextPath() %>/secure/IssueNavigator.jspa?reset=true&pid=<webwork:property value="../.." />&type=<webwork:url value="./string('id')" />&resolution=-1"><webwork:property value="/nameTranslation(.)" /></a>
            </td>
            <td align="right">
            <webwork:property value="../(.)"/>
            </td>
            <td width="60%">
            <ui:component name="''" template="histogram.jsp">
            <ui:param name="'percentage'" value="percentage(.)" />
            <ui:param name="'title'" value="./string('name')" />
            </ui:component>
            </td>
            </tr>
            </webwork:iterator>
            </webwork:property>

            </table>
            ------------------------------------------------------------------------------

            Also add, <p> and </p> in the breakdown by priority. This is for better presentation since it will put proper space around the priority stat list.

            Beiginning of the breakdown by priority:
            <%-- Do not show the "open by priority" stats if the priority field is hidden for all issues --%>
            <webwork:if test="@fieldVisibility/fieldHiddenInAllSchemes(., 'priority') == false">
            <p>
            <b><webwork:text name="'common.concepts.bypriority'" /></b><br>

            Ending of the breakdown by priority:
            </table>
            </p>
            </webwork:if>

            NOTE) There is no need to check if Issue Type field is hidden, because the field is required by default. The configuration scheme does not support hiding Issue Type field.

            2. Restart JIRA

            Regards,
            Estelle

            Estelle Kim added a comment - Hi Chris, I have found that Sam's instruction on Confluence was very helpful but I had to add a little bit more to make it work. The following is the modified instruction that I followed. Also, I have attached files at http://forums.atlassian.com/thread.jspa?messageID=257231490&#257231490 . 1. Edit $JIRA_HOME\atlassian-jira\includes\panels\browser\openissues.jsp Add the following code before the breakdown by priority: ----------------------------------------------------------------------------- <%-- Breakdown by Issue Type --%> <b><webwork:text name=" By Issue Type " /></b><br> <table cellpadding=2 cellspacing=0 border=0 width=90% align=center> <webwork:property value="@StatAccessor/allFilterBy('issuetype')"> <webwork:iterator value="./keySet"> <tr> <td valign=top width="1%"> <a href="<%= request.getContextPath() %>/secure/IssueNavigator.jspa?reset=true&pid=<webwork:property value="../.." />&type=<webwork:url value="./string('id')" />&resolution=-1"> <webwork:component name=" {./string('name')} " template="constanticon.jsp"> <webwork:param name="'contextPath'"><%= request.getContextPath() %></webwork:param> <webwork:param name="'iconurl'" value="./string('iconurl')" /> <webwork:param name="'title'"><webwork:property value="./string('name')" escape="false"/></webwork:param> </webwork:component> </a> </td> <td valign=top> <a href="<%= request.getContextPath() %>/secure/IssueNavigator.jspa?reset=true&pid=<webwork:property value="../.." />&type=<webwork:url value="./string('id')" />&resolution=-1"><webwork:property value="/nameTranslation(.)" /></a> </td> <td align="right"> <webwork:property value="../(.)"/> </td> <td width="60%"> <ui:component name="''" template="histogram.jsp"> <ui:param name="'percentage'" value="percentage(.)" /> <ui:param name="'title'" value="./string('name')" /> </ui:component> </td> </tr> </webwork:iterator> </webwork:property> </table> ------------------------------------------------------------------------------ Also add, <p> and </p> in the breakdown by priority. This is for better presentation since it will put proper space around the priority stat list. Beiginning of the breakdown by priority: <%-- Do not show the "open by priority" stats if the priority field is hidden for all issues --%> <webwork:if test="@fieldVisibility/fieldHiddenInAllSchemes(., 'priority') == false"> <p> <b><webwork:text name="'common.concepts.bypriority'" /></b><br> Ending of the breakdown by priority: </table> </p> </webwork:if> NOTE) There is no need to check if Issue Type field is hidden, because the field is required by default. The configuration scheme does not support hiding Issue Type field. 2. Restart JIRA Regards, Estelle

            Hi Estelle,

            That's a good idea. Let us know if you have any troubles doing this. Also, if you would like to increase the visibility of this feature and the likelihood of it being added to JIRA, please add your vote to this issue.

            Regards,

            Chris.

            Chris Mountford added a comment - Hi Estelle, That's a good idea. Let us know if you have any troubles doing this. Also, if you would like to increase the visibility of this feature and the likelihood of it being added to JIRA, please add your vote to this issue. Regards, Chris.

            If there is no web interface to do the job yet, I will follow the intruction on http://forums.atlassian.com/thread.jspa?messageID=257229922

            Estelle Kim added a comment - If there is no web interface to do the job yet, I will follow the intruction on http://forums.atlassian.com/thread.jspa?messageID=257229922

              Unassigned Unassigned
              07f480500bb2 Andrew Stevens
              Votes:
              12 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: