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?
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)
This works with Automation
I have did this and worked (jira cloud version). Here are the steps...
@Robert Horan , I used the When Scheduled trigger, and check if this field is empty. I have not yet added check for when the Parent issue's epic changes but I believe this can be done with When: Issue Updated.
@Yulia Zhyliaieva , There are two separate rules I set:-
1. For Bugs/Stories
When: Issue Created
project = <projectname> and Issuetype in (Bug, Story)
Then: Edit issue fields
Parent Epic Name
- Copy Epic Name from Epic issue
2. For Sub-Tasks
project = <projectname> and issuetype = Sub-task and CreatedDate > -2d and "Parent Epic Name[Short text]" is empty.
Then: Edit issue fields
Parent Epic Name.
- Copy Parent Epic Name from Parent 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
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.
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.
And that would be great if that was out of the box, didn't require another custom field to manage, and didn't require scripting knowledge :)
This workaround is great - for people who do have ScriptRunner, but not everyone does, and given the pricing, not everyone will.
Cloud users can at least make some creative use of parentEpic in () to find what they want but Server and DC users are out of luck.
Not sure if you have solved your problem, but a recent example was brought to my attention, where the Epic link was missing, but the Parent Epic was visible.
What JIRA was applying the Parent Epic as the child is linked up to the EPIC through the Parent (the Story) ie bottom upwards looking, however when I looked at the parent the subtask was not linked to the child, ie top to bottom looking.
When the later was applied, the link was visible. A little work around, but it worked.
Hope this helps
Seema is trying to do it with Automation, not scripts, there's nothing to pass over, you just need to run through adding the automation flow to do it.
Robert has pointed out that it is a little bit more complex than just a single simple automation though.
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