Hide parent key from summary column in Jira results

Question

Hello, I can't seem to find an answer to this anywhere. When I run a filter query that returns sub-tasks in the results, the summary column always displays as [parent key] / [sub-task summary]. Is there a way to not show the parent key in the summary column? It's confusing for my users as the parent key doesn't provide any useful context. They just need to easily see the issue summary.

Raziman Dom - Ricksoft · Answer

Hi @Lisa N

Since you mentioned that you are currently using Excel-like Issue Editor, you can use that app to view the sub-task's summary without [parent key] / [sub-task summary]. Simply click the spreadsheet icon on the filter results page.

You also can use our new JQL Editor feature to search the issues.

If you want to remove the [parent key] / [sub-task summary] format specifically in the filter results, unfortunately, the best solution is what is suggested by @Karim ABO HASHISH

If there is something that your team wants from filter results that are missing in the Excel-like Issue Editor, please let us know ;)

Have a great weekend!

Razi

Hannes Obweger - JXL for Jira · Answer

Hi @Lisa N

I believe JXL really shines when it comes to performance and scale (JXL will easily deal with thousands of issues and still feel snappy), and of course ease of use. There's also the many advanced features that I name-dropped above, which all fit perfectly together. Just to provide an example, it is really easy to build an interactive issue view like this in JXL, and still preserve the "spreadsheet-ness" that you know from e.g. Excel or Google Sheets:

Of course, if you simply want a plain table/list view of your issues, you can do that as well :)

The easiest might actually be to play around with it - JXL simply integrates into the project sidebar, so it's trivial to set up. You can also find more info on our website, and quick demo video here.

Any further questions just let me know!

Lisa N · Answer

Hi Karim, thank you for the link and suggestion. While the feature request isn't exactly what we're looking to do, I've added my vote as it would still be an improvement over the current display.

I understand the workaround of creating a separate custom field, but I fear it would introduce a different type of confusion for my users. If there's no setting to change it, we'll just have to live with the default Jira behavior.