Let's see if this request makes it into the Guinness Book of Records for

"Oldest Jira Feature Request"!

Please add this

I needed this, and as we have Script Runner, was able to add a Custom Field Script to do it. I detailed it here:

https://community.atlassian.com/t5/Adaptavist-questions/Custom-script-field-to-show-parent-Task-summary-in-a-filter-of/qaq-p/2064706

Upvoted, would really like to have this feature. It's hard to tell a report on sub-tasks what task/story they serve.

Upvoted! This seems like a simple change that would make a world of difference to the people who rely upon Dashboards.

This would really help me bring context of the parent task for subtask items when exporting data for reporting. These should be 2 different fields. "Parent task" field only brings subtask ID with link, no summary. A dedicated "Parent task summary" would do for me - as long as I can pull it in a report. 

In the result (list) of a filter, display Parent's Summary with Sub-Task's Summary should be nice.

Ex : 

Summary

Need to have perf tests run on build / Get CPU utilization

instead of 

FOO-123 / Get CPU utilization

The internal ID (FOO-123) is not really useful in my case. It even makes things less readable.

Thanks in advance for your help.

Regards

Danny

I agree this should be changed in core functionality, but a bump that this is available in Chrome using my free (and always will be) chrome extension "Jira On Fire" - https://chrome.google.com/webstore/detail/jira-on-fire-by-kolossi/lfdjnnoomhdlkdobmigpmhnlhaciahfi.

Various other "enhancements" too, all of which can be individually turned on/off in extension options.

Currently we're using Enhancer Plugin's Parent field to display parent's summary in issue navigator. But I believe this would be a simple and good feature if it is bundled with Jira and there won't be any need for a third part app.

The summary info of Parent ticket would be very helpful in the sub task filter. 

This would absolutely be very helpful to us as well. Please add.

I agree with @Sara Fields, this would be helpful.  It would be even better if the parent description is a separate field.

Although the javascript bookmarklet I posted before will still work, I also went the route of @Ronan.Wheeler and made a Chrome extension to do this and some other tweaks - see https://chrome.google.com/webstore/detail/jira-on-fire-by-kolossi/lfdjnnoomhdlkdobmigpmhnlhaciahfi

Not saying it shouldn't be fixed in core Jira though!

We definitely need this on our team as well. We auto-generate subtasks like "Testing" and "Documentation" for each parent issue. In our issue search results, all the subtasks have the same set of possible names and we can't tell at a glance what parent task the subtasks are associated with. It's not practical to spend a couple seconds mousing over each parent ticket number in a long page of search results to see what project each subtask actually refers to.

Very much building on @Ronan.Wheeler - rather than a chrome extension, it's possible to do this with just a javascript bookmarklet:

Add a bookmark in Chrome, any bookmark!

Edit it and change the name to "Jira Parents" and the url to:

javascript:$(".parentIssue").each(function(){ var parTitle=$(this).attr("original-title");var parText=$(this).text();$(this).text(parTitle);$(this).attr("original-title",parText); $(this).css("font-weight","bold");}); 

Clicking the bookmark will toggle parent Jira ref/parent description display (I also bold the parent).

So you do need to click the bookmark on a relevant screen rather than it happening automagically like the plugin, but YMMV whether that's good or bad. It might also be easier to use the bookmarklet if plugins are locked down?

Nice one @ronan.wheeler! An update to this (for > Edge 12 & all other modern browsers) would be to drop jquery and just use:

[...document.querySelectorAll('.parentIssue')].forEach(el => {
    el.textContent = el.getAttribute('title');
});

I started using JIRA in my new role last week and this stood out as a problem to me - I was frustrated to learn there was no solution, so I came up with my own:

I wrote a very simple Google Chrome extension with the following three components:
content.js
jquery-3.1.0.min.js
manifest.json

jquery-3.1.0.min.js can be downloaded from the jQuery website. My content.js looks like this:

$(".parentIssue").each(function(){                // find all the parent links
    $(this).replaceWith(                          // and replace each one
        "<a>" + $(this).attr("title") + "</a>"    // with it's own tooltip message
    );
});

and manifest.json looks like this:

{
  "manifest_version": 2,
  "name": "Ronan's Chrome Extension",
  "version": "0.1",
  "content_scripts": [
   {
     "matches": [
       "http://jira.intranet.mycompany.com/*"
     ],
     "js": ["jquery-3.1.0.min.js", "content.js"]
        }
  ]
}

This works perfectly for my needs, so it might be helpful for some of you too. Search the internet for 'writing a chrome extension' to read up on how to load it into Chrome. Make sure to change the URL in manifest.json to the domain for your JIRA installation, but keep the asterisks at the end.

Alternatively, if you'd like to see both the ticket number and the description, replace the third line of content.js with this:

"<a>" + $(this).text() + " (" + $(this).attr("title") + ")</a> /"

Throwing in my hat for a request on this feature. We're doing a lot of dashboards for various tracking purposes and there is no context as to what the parent feature is (since that tracks the actual work) against the sub-tasks that are mostly repetitive.

We are doing the same thing like Eddie Liu. We are prepend the parent summary in the sub-task summary. It is very unlucky for us, and redudant work. Using Jira Core for Marketing with different User different Subtaks, really needs to know the parent job in a overview.

We also have a structure where the main issue summary is more descriptive than the sub-task summary, but the sub-tasks are the ones assigned to individual. Displaying parent summary along with sub-task summary will be very helpful. A work-around is to prepend the parent summary in the sub-task summary but it is redundant imo. Thank you!

We'd love this feature as well. I don't see the harm in adding a "Parent" filter column which is turned off by default. It would add no complexity to those that don't want it, but would be a valuable sorting/organizational tool for those of us that need it.

The control of this behavior is in:
com.atlassian.jira.issue.fields.SummarySystemField.populateVelocityParams(FieldLayoutItem, Issue, Map) method
and /opt/atlassian/jira/atlassian-jira/WEB-INF/classes/templates/jira/issue/field/summary-columnview.vm template

Adding a request for this feature as well.

I would suggest to offer the following options for columns :

• Summary (New: Issue/Sub-Task Summary only)
• Parent issue Key / Sub-Task Summary (Actual behaviour)
• Parent issue Summary / Sub-Task Summary (New: Current request)

Users would then have the ability to pick and choose, which level of details they want to see in their issues list.

this would be a huge help - putting an awkward work around in place but the issue key alone isn't useful for issue summaries. An alt solution would be to add 'parent description' as an available column in the issue navigator. Then the user can decide what they want to add and when This feature would add mega-value for us - plz to be adding to teh roadmapz thx.

Can we bring this task on the road map?

Same for uns. We would be more than happy to have this functionallity

We also really ne this feature. At the moment, we really have to write the summery of the task in the summery of the subtask to have an overview...

I see that this is an old issue, but is there any ambition about continuing on this feature? Making it editable or getting it back. I fully agree with Alex Muller in regard to his statement, that showing the key only, is quite useless.

I have dashboards setup to view all tasks assigned to me. What ended up happening is that there would be tens of subtasks with the same name. Keys are not helpful to understand which project a sub-tasks correlate to. We now have users using the Parent summary in the sub-tasks summary. I realize different users may want different things, perhaps this could be a toggled option.

IMHO, this would be much appreciated by teams developing mobile applications for multiple platforms.

Most of our projects consist of a server app, iOS app and an Android app (at minimum)
Nearly all of our software features has a parent issue, which has 3 sub issues, Server implementation, iOS implementation, Android implementation.

If we just write "Server", "iOS", "Android" for summaries of subtasks, they show up in filters as dumb summaries as the assignee doesn't know what they are at a first glance.
The workaround is to duplicate parent issue's summary in each subtask summary but it is not practical and adds duplicity to the issues.

If there were an option to show the parent issue summary first then the subtask summary in the navigator, our eyes and hands using the mouse would benefit a lot from them
(The option would also improve the situation for Agile boards)

We would also like this behavior for one of our projects.

Really what we want is some way to see the parent issue summary in the search results. So either a way to add a column that shows that, or showing the summary instead of the parent issue key.

The issue of length could be handled by elipsing after a certain number of characters. That might give the person enough characters to remember what the parent issue was and then the tooltip option can still give the full summary.

I think it should be possible to define it in a velocity file so you are free to select if you want to see it or not.
The best solution for us would be a new field in the standard application Jira, compare with the parent issue summary in the plugin http://confluence.atlassian.com/display/JIRAEXT/Parent+Issue+Summary+Plugin.

Update: I saw that it is possible to add the parent's summary in the vm file.
atlassian-jira\WEB-INF\classes\templates\jira\issue\field\summary-columnview.vm

But it would still be good to have it's own parent field for sorting and searching.

We used to display the summary, but it used to take too much space and we were asked to remove it.

Martin,

If you hover over the parent - it will display the issue parents summary in a tooltip.

If we added this for every parent - it could add a lot of repeated information that is small and hard to read.

Are you trying to capture this information for printing purposes? Or just not a fan of the tool tips approach?

Regards,

Brian Lane
JIRA Product Manager