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

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

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'>

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".

Also needed for CLOUD

+1

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

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

+1

The functionality to add columns is needed especially for estimations.

+1. Much needed tool. Like many others mentioned - especially demanded for epics.

Would be great to have for estimation and possibly other columns

We want to add Resolution and FixVersion. still needed too

+1 still waiting...still needed..

Often I feel the need for estimate field so that one can easily see which stories are still unestimated and also relative size of stories under the epic.

Thanks.

+1

Request to enable additional fields under the "Issues in Epic" section like "Fix version" and "Severity"

Highly anticipated feature. We help ourselves by adding meta information to the issue title to keep an overview in the Epic view. Awkward as hell.

We would like to add 'Sprint' as a column to the 'Issues in Epic' view. Shouldn't have to buy a plugin for this. We can adjust subtask views globally so why not this? 

+1
Much needed

+

Need this feature

+10

+1

+1. Having an option to see components in the 'Issues in Epic' view would help us also getting a better overview

+1

+1

+1 for this. It would help a lot.

This seems like pretty basic functionality that should have been included from the beginning.

Opened 4 years ago, I think it might as well be seen as "not being considered" (like its linked issue)... 

It's very disappointing this feature doesn't exist.

I am surprised that something so simple has been left out of the Jira product, surely the ability for project administrator or system administrator to amend the fields displayed for the stories associated to an EPIC is not that hard. We require the need to see story points and fixed version of the stories associated to an EPIC when displaying the EPIC.

My use case is viewing time estimates in an epic in the same way I would view time estimates for sub-tasks when viewing the parent task. I'm disappointed this was overlooked and this ticket is nearly 4 years old.

This is a miss in the enhancement if they are really serious about value adds

I agree with the sentiment of all the above commenters. This is a very basic requirement.

This is a fundamental requirement, its very frustrating having to open an issue to see key pieces of information about it

Chiming in that this is very wanted by my organisation. Like CelinaK mentioned, there's functionality to change this columns for sub-tasks, why not for issues in epic as well?

We have a customer asking for this as well.

I am a bit baffled that this is 'gathering feedback'.  Adding columns to sub-tasks is existing functionality; how can this be perceived as less valuable?

Our app Exocet can help, in this article we explain how it can be used to customize how issues are visible from Epics.
This is a paid app, until Atlassian implements this feature it could be a workaround for some of you.

Hope this helps.
Christophe - Valiantys Software

Sorry... I intended this ticket to be filed under Jira Software.