• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • None
    • 104
    • 1
    • 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.

      There is no option in JIRA to add more information to the Issues in Epic section. Asking to have a way (maybe like advanced option jira.table.cols.subtasks for subtasks) to add columns either existing or custom fields to this list view.

          Form Name

            [JSWSERVER-15655] Ability to add columns to Epic Issue list on Epic

            Kevin Wang added a comment -

            I made the 350 mark. How many more signatures do you guys need?

            Kevin Wang added a comment - I made the 350 mark. How many more signatures do you guys need?

            Mosh Feu added a comment -

            It's been open for 8 years. Isn't it about time to work on this Jira team ?

            Mosh Feu added a comment - It's been open for 8 years. Isn't it about time to work on this Jira team ?

            we also need a solution for this. We need the ability to see an additional field value on stories from the Epic View

            Terri Mason added a comment - we also need a solution for this. We need the ability to see an additional field value on stories from the Epic View

            hi @pavel.kapinos, can you describe  more precisely how to deploy your solution ?

            do you use addons ?

            regards.

            Olivier LOHIO added a comment - hi @pavel.kapinos, can you describe  more precisely how to deploy your solution ? do you use addons ? regards.

            Hello everyone.
            You can use announcement banner for it.
            Script below will add column with issue type name for "Issues in epic" section.
            Jira 9 

            <script type='module'>
            AJS.$(document).ready(function() {
            AJS.$('#ghx-issues-in-epic-table tr').each(function(){
            var row = this;
            var issueKey = AJS.$(this).attr("data-issuekey");
            AJS.$.getJSON(AJS.contextPath() + '/rest/api/latest/issue/' + issueKey, function(data){
            var value = data.fields.issuetype.name;
            var status= AJS.$(row).find('td.status');
            AJS.$(status).before('<td class="nav">' + value + '</td>');
            });
            });
            });
            </script>

            for Jira older 8.7 change :

             <script type='module'>
            on :

            <script type='text/javascript'>

            Pavel Kapinos added a comment - Hello everyone. You can use announcement banner for it. Script below will add column with issue type name for "Issues in epic" section. Jira 9  <script type= 'module' > AJS.$(document).ready(function() { AJS.$( '#ghx-issues-in-epic-table tr' ).each(function(){ var row = this ; var issueKey = AJS.$( this ).attr( "data-issuekey" ); AJS.$.getJSON(AJS.contextPath() + '/ rest /api/latest/issue/' + issueKey, function(data){ var value = data.fields.issuetype.name; var status= AJS.$(row).find( 'td.status' ); AJS.$(status).before( '<td class= "nav" >' + value + '</td>' ); }); }); }); </script> for Jira older 8.7 change :  <script type='module'> on : <script type='text/javascript'>

            Dan C added a comment -

            Hello. Seeing as how this has been left open since 2016, I made a temporary solution using scriptrunner, which adds a button to any Epic issue view page, that links to a navigator view where you can sort and modify the columns.

             

            Here's what I did, if anyone wants to do similar:

            1. I added a Script Fragment (Custom Web Item)
            2. Added a condition so that it only shows on issues with issuetype of "Epic" (issue.issueType.name.toString().toLowerCase() == "epic")
            3. Set it to navigate to a link
            4. Set the link to: /issues/?filter=19500&jql=%22Epic%20Link%22%20%3D%20${issue.key}%20ORDER%20BY%20created     (notice the ${issue.key} which gets the currently visible issue key, and places it into the JQL in the URL)
            5. For the "What section should this go in", I set it to "operations-restore", which is the strip of buttons at the top of each issue (where the workflow transition buttons are), and named it "View Epic Issues".

             

            I also

            1. Created a "template" filter, and put a default JQL in there pointing to a specific epic. with JQL: "Epic Link" = "something that exists in your instance"
            2. Saved it as a meaningful name, and set view permissions to all users, and edit permissions to jira-administrators
            3. Chose "Filter" from the "Columns" dropdown, and set the columns as I want them to appear by default.
            4. Used that filter number in the URL on item 4 above (in my example, it's filter=19500, but yours will be different).

             

            You end up with a button that only appears on Epic issuetypes, to the right of all your other normal issue buttons/dropdowns. Clicking the link takes you to an issue navigator view of the issues within that epic, in a regular sortable table. You can modify the columns as a user, by clicking "Columns > My Defaults".

             

             

             

             

             

             

            Dan C added a comment - Hello. Seeing as how this has been left open since 2016, I made a temporary solution using scriptrunner, which adds a button to any Epic issue view page, that links to a navigator view where you can sort and modify the columns.   Here's what I did, if anyone wants to do similar: I added a Script Fragment (Custom Web Item) Added a condition so that it only shows on issues with issuetype of "Epic" (issue.issueType.name.toString().toLowerCase() == "epic") Set it to navigate to a link Set the link to: /issues/?filter=19500&jql=%22Epic%20Link%22%20%3D%20${issue.key}%20ORDER%20BY%20created     (notice the ${issue.key} which gets the currently visible issue key, and places it into the JQL in the URL) For the "What section should this go in", I set it to "operations-restore", which is the strip of buttons at the top of each issue (where the workflow transition buttons are), and named it "View Epic Issues".   I also Created a "template" filter, and put a default JQL in there pointing to a specific epic. with JQL: "Epic Link" = "something that exists in your instance" Saved it as a meaningful name, and set view permissions to all users, and edit permissions to jira-administrators Chose "Filter" from the "Columns" dropdown, and set the columns as I want them to appear by default. Used that filter number in the URL on item 4 above (in my example, it's filter=19500, but yours will be different).   You end up with a button that only appears on Epic issuetypes, to the right of all your other normal issue buttons/dropdowns. Clicking the link takes you to an issue navigator view of the issues within that epic, in a regular sortable table. You can modify the columns as a user, by clicking "Columns > My Defaults".            

            FK added a comment -

            Also needed for CLOUD

            FK added a comment - Also needed for CLOUD

            Joe Webb added a comment -

            +1

            Joe Webb added a comment - +1

            Sridhar added a comment -

            Request to enable any custom fields under the "Issues in Epic" section like "Team" "Select Team"

            Sridhar added a comment - Request to enable any custom fields under the "Issues in Epic" section like "Team" "Select Team"

            Drew McL added a comment -

            This would be a really great feature and would really help with some of our planning activities! +1 from me

            Drew McL added a comment - This would be a really great feature and would really help with some of our planning activities! +1 from me

              Unassigned Unassigned
              e3ab14e6a3a1 Anthony Breeden
              Votes:
              351 Vote for this issue
              Watchers:
              143 Start watching this issue

                Created:
                Updated: