Display "Epic Link" in Sub-Task detail view

[Normen Müller]

Being on, e.g., `https://<site>.atlassian.net/projects/<key>/issues/<key>-<#>?filter=allissues` is there an option to have "Epic Link" on the detail view of a Sub-Task. That would be of great benefit for gaining quick context while browsing through all issues. 

BR, /nm

[Amy Likoravec]

Hi there, has this problem been fixed? I would also like to see the epic link displayed against associated sub-tasks.

Thank you!

[Piyush Pangtey]

This is critically required.

[NIKOS KARANIKOLAS]

I totally agree that it is important to be able to see in which Epic the Subtask is relevant to. Otherwise the Boards presantation is useless for Sub-Task, as you can not see where each sub-task belongs. Sometimes the Task-parent is not enough information.

[Shweta Singh]

Very much needed in Jira Software.

[Michelle Påhlman]

The need here would be for teams that do no estimates and only do issue count on sub-task level not on story level since this is not detailed enough. the idea would be to see how manny subtasks for a specific epic is done in a sprint to calculate cost relations and other progress. It would not be used as a hierarchy tree configuration rather then a filter configuration. I would say that is why it is needed. I think this was possible years ago and it has now been removed. But there are workarounds that could work. But it will take time to add.

[Nic Brough -Adaptavist-]

Um, sub-tasks are not sprint items.  Their status is not relevant to an Epic directly, it only matters as part of contributing towards their parent story's completion status.

[Felix DRS]

It´s not as you say, of course that their status as other type of tasks is relevant to an Epic and to an any way to manage workload of your team.

[Nic Brough -Adaptavist-]

Nope. 

I think you have misunderstood what a sub-task really is.  Specifically, they are not sprint items (and therefore not something you need to look at when managing workload or scoping an Epic)

[Thomas Deiler]

Dear @Normen Müller,

the custom field epic link is restricted to stories (and probably other issue types) and not visible for any sub-issue type. This is configured by default like this.

You could manually override this configuration, but I really cannot recommend. Sub-task are linked to parents and not directly to epics.

So long

Thomas

[Nic Brough -Adaptavist-]

I wouldn't do that either, it could break in interesting ways.

However, I would see no problem in using something like Script Runner to provide a copy of the text in the Epic Link field on the sub-tasks.  That could then be used in boards.

[Normen Müller]

I'm on Jira Cloud. Still possible?

@Thomas Deiler As to me I believe "the custom field epic link is restricted to stories (and probably other issue types) and not visible for any sub-issue type." is not a good restriction. Imagine a lot of tasks and sub-tasks on a board. To gain a quick overview to which "context" those tasks/ sub-tasks belong a colorful presentation just helps. So colored epic links AND colored labels would be of a great benefit --- no matter if it's a task/sub-task/story/ ... 

[Thomas Deiler]

Dear @Normen Müller,

I totally get you, but it makes no sense. Atlassian introduced the epic as a kind of level above issues. So logically, issues can be linked to epics. Sub-issues where already linked with the parent relation. Over the path from epic link and parent link, the information is complete. Linking sub-issue to epics would build up redundant information. Than the whole thing is not any more  a tree but a network.

What can help in your situation is, to introduce a swim-lane on epic level - then all in one block is visually divided from the rest.

so long

Thomas

[Normen Müller]

Hi @Thomas Deiler,  as to me, it's more about presentation rather than representation. I totally agree not represent redundant data, but that does not relate to what we present. So I still vote for having the option to /display/ those labels on sub-issues. Cheers, /nm

[Thomas Deiler]

Dear @Normen Müller,

understood - best you create a suggestion (https://jira.atlassian.com) an hope that it will get picked up.

so long

Thomas

[Berri]

I would like this as well.