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; } } }

Comment editor blocks scrolling in Jira

Stan Merezhko

When writing a long comment, the editor box is now set to position:sticky, which keeps it fixed on screen. This prevents scrolling down to see previous comments while drafting.

This is especially disruptive in issues with long discussions where referencing earlier comments is necessary.

Is it possible to remove or disable sticky behavior, so the editor scrolls naturally with the page?

Accepted answers

All comments

Jeroen Poismans

Hi Stan and welcome to the community.

I haven't experienced this behaviour myself since we tend to keep the comments short and to the point, but there is no such setting,

Here is something you can try: Reverse the order of the comments (new on top vs new on bottom), see if this maybe changes the behaviour of the UI to a more acceptable way?

Stan Merezhko

Hi Jeroen,

I believe this is a recent change. I only discovered it today.

We need to post lots of images in comments. Once you add one or two screenshots, the editor grows to take up the entire screen and completely blocks scrolling.

Here's what it looks like:

Reversing the order doesn't help - the comment box moves to the bottom of the page, but it stays sticky.

Nikola Perisic

Welcome @Stan Merezhko

Sadly,no. It's hard coded and cannot be changes. Even if you try to do this with deleting it from the inspect element, the changes won't be applied. Have you tried zooming out?

Stan Merezhko

Thanks!

This change is the opposite of a QOL improvement - it makes working in the comments harder. I really hope Jira reverses it, because this is clearly a bad decision.

Sandy Spink

I would also like to see something done abot this. Maybe an option to minimize the comment box at least so I can minimize, read comments, maximize, write, etc.

Roberson Eduardo Bergamaschi

Shameful update, this is a pain when you deal with long tickets. Needs to be reverted ASAP.

Bruno Potyguara

I thought it was a bug in first place, and I just found out that apparently this is an intentional change. I usually need to write long comments and refer to previous ones to elaborate. Now, I have to duplicate the tab on my browser: one to comment and another to read past comments. This update has had a real negative impact on my workflow, would be good to at least allow the user to disable the sticky behavior.

Stan Merezhko

If you are using uBlock Origin, add this filter to disable the sticky behavior:

atlassian.net##div:style(--_d564on: static !important)

But this is not a long-term solution, of course. Atlassian needs to revert this change, or at least give us a setting to disable it.

valentinas_pusvaskis

Even worse is when your comment is longer than whole screen. I copied my previous comment with whole table of test cases. I cannot reach the bottom of my own comment.

Greg Neumarke

I agree this needs to be reverted or given a setting to turn it off. For me, I think this is only happening on a brand new comment.

Possible workaround: If I start a comment, then save it, and go back and edit it, I can scroll up and see previous notes.

Gennady Gandelman

Want to add my own wtf to this. It doesn't even have to be a long comment if you are on smaller screen size. Can't see the comment just prior to which I'm trying to respond. Atrocious usability downgrade. It needs to be dealt with!

Paul Hanetzog

Experiencing the same behaviour myself and among colleagues. Today is the first day we experience this behaviour of the comment box.

We are considering contacting Atlassian Support.
I am opening tickets on my second screen, or I have to cut & paste my comment a few times if I want to read previous comments.

This is ridiculous.

Greg Neumarke

To expand on this for those new to uBlock Origin:

This doesn’t work in Chrome, since it only supports uBlock Origin Lite. You need the full uBlock Origin to make “cosmetic” changes to already-loaded web content.

This may be the final straw that moves me from Chrome to Firefox. Firefox can still run the full-strength uBlock Origin. For the moment, Edge can still run it, too.

With uBlock Origin installed,

click the uBlock icon to open the extension
click the gears icon
click the tab “my filters”
Ensure “enable my custom filters” is checked (I think that it was on by default.)
Add the custom filter by pasting this line into a blank line in the numbered list of custom filters:
```
atlassian.net##div:style(--_d564on: static !important)
```
This changes the “position:sticky” to “position:static” on the relevant part, and allows the new comment box to scroll again.
Click “apply changes”

Roberson Eduardo Bergamaschi

Congrats again Jira team, you made it worse than before with this new floating WYSIWIG fixed tab. You really need to revise the team behind those changes...

Aleksandr Markovskij

Is there any way to fix it? I'll be happy to use Greasemonkey or the like to fix this issue, but can't find what parameter to override. Any help will be appreciated.

Stan Merezhko

See this comment:

https://community.atlassian.com/forums/Jira-questions/Re-Re-Comment-editor-blocks-scrolling-in-Jira/qaq-p/3098827/comment-id/1144964#M1144964

Aleksandr Markovskij

Thank you, how did i miss that. I don't use ublock, but this will definetly help!

Gennady Gandelman

Thank you! Btw, supported by Brave which is excellent imo.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud