Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Display Epic Link on a subtask

Hi! I would like the subtasks to display Epic link.

Say a lot of discussions about that, still need to do that. I have stories with three subtasks assigned to different developers. I want to look at the board and see exactly who is working on which epic, it is not so clear from stories.

I am configuring the issue screen view, there is Epic link field, but it is not visible, and I cannot therefore fill it. 

I know that JIRA automatically does not assign a subtask to an epic, understanding that it is part of a user story and a user story is part of an epic. Still I would llike to create an automation rule and copy the epic link from a story to its subtasks.

Is there a workaround for me to be able to see the epic link on a subtask?

4 answers

1 accepted

1 vote
Answer accepted

This one is a pain - whilst I know we can, and should, infer data from parent issues, I do not like that we can't derive it automatically in Jira.

Yep, it's fine that a sub-task is clearly part of an Epic because its parent is, and it should be in the same version(s) as its parent, the same sprint, and so-on, it's pretty dumb that we can't report on that clearly.

I have to admit that for Server, I wrote an app that created derived fields that solved this (and the summary/key/sort issues that are similar).  Nowadays, as an Adaptavist, of course, I do it with Scriptrunner.  SR for Cloud can also do scripted fields that might work for you.

But I think you can do it with Automation too - have a text field for "global-epic-link" that copies the content of Epic Link on to every issue using it (don't just do it for sub-tasks, it's a lot more useful if you can use JQL like "global-epic-link = 'my epic'" and get all levels of issue)

You would get multiple issues from reporting to the actual issue if you were to achieve that. As you have already said, an epic has multiple linked issues, and those issues can have multiple sub-tasks reports and other functionality is based on these links working in this specific way. 

If you have a board sorted by epic with issues that have sub-tasks then those sub-tasks should also be shown as separate issues and there should not be an issue to see which dev that you have assigned 

subtask.JPG

Hi, I think you missed where this problem occurs. It's not the on the kanban/scrum boards, it's the issue view (eg if you share a link to a sub-task).

In my project each epic (product) has, more or less, identical stories (ie there's a standard set of tasks for a product). When viewing a subtask directly, my team have to hover on the breadcrumb to even see which story but it still is not obvious which product they relate to without navigating away.

Yep, that's why I add a scripted field for displaying it!

That scripted field is $$$ for people without SR

@Robert Horan 

As an Adaptavist, I agree with you, the best way to fix the problem is to get Scriptrunner, but it does cost.

As someone remembering their non-Adaptavist days, I agree with you, this is something that should be built-in.  When a sub-task takes its values from its parents, it should show them.

Like Robert Horan likes this

So let's say someone does get SR to do this, is there an out-of-the-box script they can adapt easily without knowing Groovy? 

This is more than theoretical, I might need to provide this as a solution :)

Hi @Yuliia Zhyliaieva

Have you sorted this out using Automation? I'm very interested in your approach to this. 

Thanks! Pablo

Hi,

This works with Automation 

I have did this and worked (jira cloud version). Here are the steps...

  1. Created new text field "Parent Epic Name" to Story and Sub-Task screens.
  2. For Story, Copy Epic Link from Epic Issue to Story's "Parent Epic Name" field.
  3. For Sub-task, Copy "Parent Epic Name" from Parent Issue to Sub-task's "Parent Epic Name" field.

Thank you,

Seema

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you