nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Stop comments from collapsing

unknown

Wondering if there is a setting to adjust to stop comments on an issue thread from collapsing, where you have to click 'view additional comments'. Our users frequently overlook this because it blends in so well, looking for a way to stop the platform from collapsing them and just leave them all viewable without expanding. Thanks!

Accepted answers

Michael Thompson_ndzw0i

I'm not sure when this option was introduced, but I'm using Jira Software 8.1.0....

Click on the Administration cog and click System.
Click the Advanced Settings button.
About 3/4 of the way down the page you will see a property key jira.comment.collapsing.minimum.hidden. If you set its value to 0 it will stop comment collapsing.

All comments

Michael Thompson_ndzw0i

I'm not sure when this option was introduced, but I'm using Jira Software 8.1.0....

Click on the Administration cog and click System.
Click the Advanced Settings button.
About 3/4 of the way down the page you will see a property key jira.comment.collapsing.minimum.hidden. If you set its value to 0 it will stop comment collapsing.

Steven F Behnke

Keep in mind that if you disable this and you find an issue with hundreds of comments, the issue will load SLOWLY AND you will incur excessive load on the server. The feature was introduced for a reason.

Bill Sheboy

Hi @Steven F Behnke

Would you please share where you learned about the impact of altering this setting? I did not see that information in the Jira documentation. Thank you.

Steven F Behnke

Through experience. In particular it was a ticket that had been imported from another piece of software, and that ticket had been used as a piece of documentation so it had grown quite a bit over a long period of time.

Jira Server renders the HTML serverside. If you turn collapsing off, the time spent on the server rendering the content is longer, additionally if/when the comments are loaded in dynamically that javascript operation will also be much slower.

It's quite trivial to test -- turn the comment collapsing off and then use a script to add many many comments.

I understand the server load problem. But, assuming the comments were expanded, the content will be loaded and cached for that user/browser. In that situation, the user should have the option to keep the comments expanded until they leave the issue.

I find the list gets collapsed each time I save an edit. It's tedious to have to keep re-expanding and scrolling the list after each edit.

I also understand caching and stale data and all the rest, and that this is a very particular nuisance, but wanted to vent because I have been dealing with the nuisance this quite a bit today...

Rob Calhoun

The setting to prevent comments from collapsing does not work. (Tested with Jira Cloud as of 2022-10-28).

Setting:

Screen Shot 2022-10-28 at 10.51.56 AM.png

Result (no change):

Screen Shot 2022-10-28 at 10.52.46 AM.png

We migrated from an older on-prem version of Jira and this issue is everyone's number-one complaint.

The most common frustration is it results in a failed search:

Search for a term using Jira search
Jira returns a list of tickets
Click on the ticket, search for term using browser search.
Term not found (!!!) because it is hidden from view.

Everybody hates this. Just show us all the data we put into the ticket.

Regarding slow rendering: yes, Jira Cloud is very slow. That is a different problem and largely due to poor use of CSS. The decision to hide comments and (evidently) break the documented means of disabling this feature means that we wait for the slow load, then click "show n more comments", then wait again. The net result is that Cloud Jira slows users down more by hiding comments than it would by just showing them.

Rob Calhoun

Just realized this is the community forum, not the Jira Cloud bug reporter. The ticket for bug on this issue on the JIRACLOUD project is https://jira.atlassian.com/browse/JRACLOUD-44911 .

Daniel Hong

Doesn't work for us either. And it looks like that ticket is a request make the option per user setting, which we don't need. We just need the global option to work!

Edit: Ah, it was cloud environment for you. We are using the on-premise server version.

Anatolii Kunaev

It would be better if there were a parameter that shows the whole page, like

'https://url/TICKET-15?page=full'

It would significantly ease the life.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

jira

jira-software