Turn off header rows for subtasks in issue view

Question

Hello everyone.
Since today we see a header line above the list of sub-tasks in our issues.
This line takes up a lot of space and we don't need it.
The community posts on this topic are over 10 years old and no longer helpful.

How can I deactivate this 'feature' again?

Thx
Andreas

Dirk Lachowski_b0vz9b · Answer

@Karan Sachdev Tried this new feature now for a day - and I hate it. Maybe it's because it has been an old issue, but it feels as if it has fixed a problem that already has been fixed a long time ago - but in a different way. After this change, viewing an issue with sub-issues in the side panel (the slide out thingy) is completely broken. Information is lost and i have to switch to the full page view:

Having this feature before there was a slide-out issue view may have been a good thing. But slide out issues combined with this is just madness. It's great in the issue full page view, but if the issue is in a side panel, just give me the old behavior.

Same problem if you have an issue open in full page view and open a Confluence page in the sidebar:

So, maybe some media queries that revert the display to the old view if screen real estate is limited.

Dirk Lachowski_b0vz9b · Answer

@Karan Sachdev For a future iteration, maybe make the header opt-out while still having the ability to select fields? The header adds a lot of visual noise, and somebody who has changed it from the default should know what each field is. And because the field selection is per user, there’s no information loss if the header is removed. Just add a toggle for it to the field selection dropdown.

Also: On smaller displays, having the config trigger in a table column eats up a lot of space. Maybe move it up to where the add subtask “+” icon is?

Karan Sachdev · Answer

Hey Andreas, Markus,

Could you please confirm if you're referring to this?

If yes, this was a part of an experiment, and roll out began to some randomly selected sites in the last week of Feb.

It looks like this will address the suggestion ticket: https://jira.atlassian.com/browse/JRACLOUD-70206

Thanks!