You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi. Is it possible to see the parent of a subtask in a separate field? I know I can see the parent in the breadcrumbs, but in order to do that I need to hover over the breadcrumbs, see the popup, and possibly go to the task itself. I would like to see a separate field with the name of the parent for the subtask.
Also is it possible to see the subtask to which epic it belongs in a separate field?
Hi! Have exactly the same issue and ended up here while googling it.
Not sure if a solution to this has been found in the meantime, but if so I'd be interested.
As @Alexey Nechaev said, the ParentIssueKey field doesn't exist in our Jira (and I guess it's not a default one) and the Parent link field doesn't work for Sub-Tasks (but I'd expect that one to be the right choice).
What the red marked text suggest also doesn't make much sense to me or is at least not what I'd expect here.
Norman
right? why would I need to explicitly set the parent of a sub-task?
to be clear, when looking at the user story, I can see the list of its sub-tasks.
it doesn't seem to be working the other way, however: when on the sub-task, I lose the linkage back to the parent user story.
horrible ux.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In my case I acted like this:
go to the list of issues. add columns to the list: parent, parent link. And there was no parent in the problem sub-tasks. It's look like they just lost parent.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am also mssing this. The visualization and controls for managing the hiearchy of epic>story>(sub)tasks are absolutely terrible in Jira, cannot understand why this is such a mess.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Seems like quite an oversight. Having to hover over the parent breadcrumb doesn't take long but doing it 100s of times per day is infuriating.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Alexey Nechaev and welcome,
For the parent-subtask issue, you can use the ParentIssueKey field (just add it to the appropriate screens). It will only show the project key of the parent issue.
For the epic - subissues relation, you can see that from the epic link field. If not visible, then add it to the screens.
Does this solve your problem?
Alex
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can't see ParentIssueKey field here. Is it custom field? And if it is displayed, then only the key, not the name?
https://www.loom.com/share/f48502b6147941da9b36a90bb3434445
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am using data center. Not seeing "ParentIssueKey " as system field. And "parent linK=k is not fetching value of Story or Epic the subtask belongs to.
We have advanced roadmap license, still this is not available.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
same problem here. this used to just show up on sub-tasks by default.
in my jira instance, I doin't even see the breadcrumbs that used to be at the top of every ticket in sub-tasks, nor am I able to add ParentIssueKey or anything like parent.
I have a very limited set of fields to select from.
who ever thought it would be a good idea to remove the parent information from a sub-task? the clue is in the name!
feels like a big regression to me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.