JIRA issue navigator cannot show parents of issues but it is able to show sub-tasks. An oversight or my misunderstanding?

Ian Mayoh June 18, 2013

In issue navigator, I can select 'sub-tasks' as a column to see a list of sub-tasks that belong to an issue. However, the opposite is not true. There is no 'parent' column that can be selected to show the parent of the sub-tasks. It seems strange that one has been done without the other.

3 answers

1 accepted

3 votes
Answer accepted
Renjith Pillai
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 6, 2013

Code for scripted field for Script runner

importcom.atlassian.jira.ComponentManager;

defburl = ComponentManager.getInstance().getApplicationProperties().getString("jira.baseurl")

return (issue.parent != null) ? "<a href=\""+ burl + "/browse/"+ issue.parentObject.key + "\">"+ issue.parentObject.key + "</a>" : "";

Radek Janata January 30, 2015

For experienced scripting admins it's obvious but beginners might overlook the missing spaces typo on the first two lines: import com... def burl... However, thanks for the answer, this helped me a lot.

Stephan Hostie February 9, 2015

And for unexperienced, what is the template to be used?

1 vote
Marcus Widerberg March 28, 2014

<RANT> This is clearly an oversight or handicaped by design. In excel, you need the parent id column to work with the data effectively. Excel cannot use comma separated list of child references in a column, such as the "subtasks" column. Either this is done on purpose or a sloppy implementation coming out of a lack of understanding of how excel works, in other words an incompetent implementation. Yet another jira "feature" that needs scripts and workarounds... GAH! Why did we choose jira a month ago, do we do a rollback of all this work and all of these workarounds... </RANT>

Marcus Widerberg March 28, 2014

Including a parent reference in the dataset has been rejected by atlassian, this is the "new feature":

https://jira.atlassian.com/browse/JRA-21555

1 vote
Jobin Kuruvilla [Adaptavist]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 19, 2013

In the case of subtasks, you can see the parent key in the summary column. Even the summary of the parent is shown if you hover over on the key.

In JIRA6, detail view makes it even better.

Just a different implementation!

Ian Mayoh June 19, 2013

Sorry Jobin but this is not what I am talking about. if I do a search, it is so that I can find the parents of a set of sub-tasks. For example, if using GreenHopper, I have user stories and they have work items defined as sub-tasks. In issue navigator, I want to do a search for some sub-tasks in sprint x and I want to see, IN THE SEARCH RESULTS, what the parents of those sub-tasks are, i.e. the stories to which they belong. This is not possible as there is no appropriate column to select for search results. You are right - there are many ways that I can find out the parent of a sub-task. That's not what I want to do. I want to be able to list a filtered set of sub-tasks and see the parents of all of them at once. That way, I can output as report or use the filter in a gadget on a dashboard.

Jobin Kuruvilla [Adaptavist]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 19, 2013

You will have to capture the parent field in calculated custom field. You can write your own calculated fields or use the scripted fields from plugins like Scriptrunner.

Andy Dingfelder February 26, 2014

do you have any examples of writing your own calculated fields, espessially in onDemand jira?

sean o'brien May 21, 2018

This makes searching for subtasks that are repeated for most stories (Create Unit Test for example) pretty much useless.  A Subtask has no real context unless the parent issue is included in the search results. This is a defect.

 

jiradefect.png

Suggest an answer

Log in or Sign up to answer