Hello everyone, we also encountered this situation in Jira server (v9.12.4)

Just turned on this module and everything worked.

–

Update. Investments did not improve. Go to the section Manage apps -> Jira Service Management And enable module serve-desk-comment-field

JRASERVER-74122: Since version 9.4.0 caused significant issues within the user community, and these were addressed in version 9.4.6, this problem JRASERVER-77658 is likely to be annoying for them again.

JRASERVER-5443: The manual changes made by users to the comment sort order will now be retained in the user profile. This means the sorting order setting will remain the same until the users change it again.

While the user profile will honor these specific changes, we want the default sort order to be "Oldest first." Therefore, JRASERVER-77658 is the bug affecting us. I strongly believe that the priority and severity of this bug should be increased.

The sticky comment footer feature is cool!
If the comment box can be canceled by pressing the 'Esc' key, and occupy less page space then it would be better.

The fixed version includes v9.4.6 which is the version this site uses. 

However, there seems no difference for the comment box.

My userscript https://greasyfork.org/scripts/472161 might help some people following this Jira issue.

We have identified that cause mentioned in the previous comment. When we further troubleshooted we identified that this feature works when Zephyr Squad Plugin is disabled. We have Zephyr v9.1.6.91609670 installed.

By enabling the dark feature I see the comment box is sticked in v9.4.6, however stickiness is not adhering in v9.4.7. Is the behavior same for everyone ?

I noticed with "Old First" sort order, I have "Load 10 older comments" at the top while viewing comments. Then if I switch to the "History" tab, it switches to "Load 10 newer comments" at the bottom. Is there a bug tracking that issue?

Is this feature delivered as dark feature even for 9.6?

The sticky dark feature is cool, but it can occupy less page space as follows (The picture is a modified screenshot):

https://imgur.com/a/rwKwM1h

Hi, everyone, please record to enable the dark feature with the .enabled in it!

com.atlassian.jira.commentStickyFooter.enabled

I found that this was caused in our case by our CDN. Disabling the CDN resolved this. Enabling it after also seems to show the correct position for the comment bar again. Might be a cache related problem in that case.

He's correct in that it is ever so slightly offset to the right, but nothing's cut off and it's still usable

Oliver, your image isn't showing to me, but I checked my kanban board and the sticky comment looks fine. Using 9.8.1 and Chrome and tried resizing the board/ticket border and it always filled the bottom correctly.

The feature does work for us, however the sticky comment footer does seem to be a bit buggy when looking at at kanban board view. It's placed slightly off to rthe right of wher it should be. Does anyone else see it show up like this?

The feature does not work for me on these browser versions:

Chrome Version 113.0.5672.92
Safari Version 16.4 (18615.1.26.110.1)

I do not have any extensions/plugins active in those browsers.

mine is Version 113.0.5672.92

Works fine for me in Chrome Version 113.0.5672.64

I am seeing the same thing. The Sticky Comment Footer dark feature works in Firefox, but not in Chrome OR Safari.

Is something special required to get this functionality in Chrome/Safari??

Hey Team, sticky comment footer is not working on Google Chrome but works in firefox.. Anyone facing the same..

b731196ffccf In 9.4.6 this feature is hidden behind the feature flag (a.k.a. dark feature). To turn it on you need to add com.atlassian.jira.commentStickyFooter.enabled entry. Here's the documentation on how to do that: https://confluence.atlassian.com/jirakb/how-to-manage-dark-features-in-jira-959286331.html

Hey Roman, after the upgrade to 9.4.6 version we are not seeing the comment button position change.. it still shows the same as earlier i.e it's below activity panel.. Am i missing something..? 

Thank You. I was missing the .enabled. Appears to be working now. Works fine on chrome and firefox for me.

the sticky-comment-button-feature seems to work only in fireforx, not in chrome (113.0.5672.93) or edge (113.0.1774.35)

You have to add "com.atlassian.jira.commentStickyFooter.enabled" to the dark features  After that it works without a restart of jira

We know how to turn on dark features, however adding that com to dark features does nothing, so the question is, is it enabled via that or set in Jira properties as mentioned previously. I don't think anyone knows for sure.

a684c3486161 Here you can find the information on how to turn on any feature flag (a.k.a. dark feature), including the one responsible for sticky comment footer: https://confluence.atlassian.com/jirakb/how-to-manage-dark-features-in-jira-959286331.html

Hi, can someone clarify how to enable the com.atlassian.jira.commentStickyFooter feature flag. We are running 9.4.6 and I'm not seeing a place to enable the feature flag (I'm not seeing it under advanced settings). We are also running JIRA Server as opposed to data centre if that affects it.

Hi Folks!

9.4.6 was released yesterday so the issue should be fixed now. For more details you can refer to the resolved issues notes here: https://confluence.atlassian.com/jirasoftware/issues-resolved-in-9-4-6-1236437539.html

Thanks

Roman

It's because they havn't changed the fix version on this ticket to show 9.4.6, sometimes it takes them a day or two to include things I've found

Jira 9.4.6 was released today, but I do not see the fix for this included. Was it included (and just not marked as such), or was it actually left out of 9.4.6??

Estimated release timeframes: May 8-12, 2023

Source: https://confluence.atlassian.com/jirasoftware/jira-software-release-notes-776821069.html

When is 9.4.6 LTS being released?

Just read the "Current Status" -> both fixed in 9.4.6

Will this be backported to the 9.4 LTS release?

I upgraded our test system to 9.8.0 and it seems to be fixed.

I see that Jira 9.8.0 is out today, and it advertises changes to the commenting behaviour.  Can anyone confirm that the issues are fixed, as described here?

It is ironic that the comment button and the bundling of old comments is exactly how we want the newest versions to acts when we are making comments on this enhancement ticket. LOL. Please allow this to be a configuration for the comment button to appear at bottom and/or top, with the ability either to bundle old or new comments which corresponds with button placement for ease of use with least amount of confusion. 

Starting from Mario Mächler and Uwe Schindler scripts, I created this mutation observer can be installed in the Announcement Banner by a Jira Admin.
It will move the Add Comment (if the default newsest first is selected) for:

1. Jira Software in Full View Issue mode, Agile Boards (it won't work from Search > Detail View navigation)
2. Jira Service Management in Full View Issue Mode, Queues, and Kanban Boards

Hope this helps until we get a more native feature.

<script>
//move comment box position workaround for the new sort order of comments
document.addEventListener("DOMContentLoaded",() => {

function moveCommentPosition(){
	try {
        console.log("Trying to move comment position");
		var commentDiv = $("#addcomment");
		var sortOrder = $("#sort-button");
		if((commentDiv.prev()[0].id == "activitymodule" || commentDiv.prev()[0].id == "commentmodule") && sortOrder){
			var orderDirection = $(sortOrder).data("order");
			if(orderDirection == "asc"){
				commentDiv.prev().insertAfter(commentDiv);
                    AJS.$("#issue-comment-add").css({"padding-bottom":"inherit"});
			}
		}
	} catch(e){
		//console.log("The comment div is not present here")
	}
}
	// observe mutations on the page
	const targetNode = document.getElementById('page');

	// Options for the observer (which mutations to observe)
	const config = { attributes: false, childList: true, subtree: true };
    
	// Callback function to execute when mutations are observed
	const callback = function(mutationsList, observer){
    for(const mutation of mutationsList) { //activity-comment is in JSM, mod-content & ghx-detail-contents class is in Jira software
        if (mutation.type === 'childList' && (mutation.target.className.indexOf("activity-comment") > -1 || mutation.target.className === "mod-content" ||  mutation.target.id === "ghx-detail-contents")) {
            moveCommentPosition()
        }
    }

};
// Link the observer to the callback
const observer = new MutationObserver(callback);

// Start observing
observer.observe(targetNode, config);


});
</script>

Atlassian should make progress of JRASERVER-74440 as well

Yep.  That backwards behavior of showing the oldest comments is what I mentioned above, and is what JIRASERVER-74191 is about.

Here we decided that the behavior with "asc" was ultimately even more confusing and annoying than "desc".  Which is saying something.  Hopefully the fixes upcoming will resolve these issues and get us back to something similar to the 8.x behavior (even if we need to set this advanced option to achieve it).

Ah yes, I have just played with it myself and you're correct, changing that value does change the default behaviour of the comment ordering. However it works in the opposite way as expected for users of Jira 8.x.

In 8.x, we had it set to Descending. This meant the newest comments would be at the bottom, immediately above the Add Comment field. Crucially however, in Jira 8.x it would HIDE all of the oldest comments behind a "Load x comments" button, and show the most recent 5 comments. That was sensible behaviour.

Upgrading to Jira 9.x with this set to Descending, it will load only the 10 oldest comments and hide the most recent comments behind a Load x comments button.

So yes, the upgrade from 9.x inverted the usefulness of this global setting.

IMO there was nothing wrong with Jira 8.x behaviour. If you want to increase the performance of comments for 8.x, then I would say throw out the current design in 9.x because it is confusing and weird, and start from 8.x and make changes to that.

In my instance of Jira 9.4.4, jira.issue.actions.order does work.  If you change it to asc then the default order will be from oldest to newest (ascending), not newest to oldest (descending).  Unfortunately that doesn't work so well since then it will show the 10 OLDEST comments, not the 10 newest comments, which is bogus.  So this is a lateral move at best.

See JRASERVER-74191

IMO you should just revert to Jira 8 behaviour entirely. It already didn't load all comments and hid them behind "load more" buttons, and everything worked fine and users were already familiar with it.

At the least, you should simply change the first "Load 10 comments" button to also support the shift-click ability to Load All. After all, if you care about performance, forcing users to click Load 10 and then Load All when they wanted to simply Load All to begin with, is forcing the server to deal with 2 requests instead of 1, and forcing users to waste time clicking a button twice instead of once.

Finally, "jira.issue.actions.order" is an Advanced setting to change the default sort order of these action items. In Jira 9.x this setting seems to be ignored, with these views defaulting to Newest First. This is a clear regression in behaviour when Jira ignores a system-wide setting that is supposed to control this behaviour. Fix it.

Hi all,
I wanted to give a quick update as to how we are addressing these two issues and when you can expect these issues to be fixed.

1) Sortation issues

The plan is to address both sortation issues in LTS bug fix version (9.4.6) The fix will address which comments are sorted when a user changes oldest to newest. We will partially revert back to old Jira 8 behaviour where only the visible comments will be sorted. However, we will be keeping the progressive loading behaviour which was implemented originally for performance stability improvements. This fix will also address the change of sort order if a new comment is added. Given the potential performance implications of comments - a little extra time is required to develop this fix.

2) Add comment button
We will also fix the position of the new comment box/add comment button. This fix should make it easier for users to add comments to issues. This will be release in 9.8 and also in 9.4.6

@Matthew Price - I already have that set to 'desc' and upon logging out and back in, the comments go back to ascending.

Was just checking ot see if the location of comment button had been changed yet in the latest version  sadly no.

@Richard Cross  you can revert to desc by going here if that helps [Change the default order for comments | Atlassian Support|https://support.atlassian.com/jira-cloud-administration/docs/change-the-default-order-for-comments/]  

This is embarassing... we've just upgraded from 8.22 to 9.4 and customers aren't happy.

Newest comments at top, but the add new comment box is at the bottom... how did that get past QA?

And there's also a "Load 10 newer comments" bar... which says that regardless whether it's hiding 1 new comment or more than 10.

And the new status/transition selector is extremely confusing.

@Maro & @Uwe:

Thanks for these scripts. I haven't been able to install the script runner one, it complains that "Could not find })(AJS.$); in configured resource directories:"

I've just spent the last 2 hours trying to customise Uwe's version with jsIncluder but have been unsuccessful. I'd like to modify it in these ways:
1. If the comment-sort button exists, and the sort type is asc, then move the "Add comment" button above the activity box, ie the current behaviour of the script,
2. else if, the comment sort-button exists, and the sort type is desc, then keep the "Add comment" button where it is, but change the "Load 10 comments" button to instead be one that says "Load 10 comments. Shift + select to load all" so that the user only has to click once to see all the new comments, and not click, scroll, click.

I've also found Jonathan Fielder's tamper monkey user script from JRASERVER-5443 which works, but that requires users to install an extension and set up scripts etc, so is not suitable for the majority of my user base.

To me this change was wholly superfluous and has just resulted in lots of complaints from my users. We have just upgraded to 9.4 LTS and hence why we've run into this issue. We were planning to migrate to data center later this year but this gives me yet another reason to consider alternative solutions.

Frankly I think Atlassian should just revert the changes they made to comment ordering/loading, I don't know what was wrong with the behaviour in Jira 8, and it already would paginate and hide a lot of the comments unless a user clicked on a button to load them all. It would be nice if Atlassian actually fixed REAL ISSUES affecting the product such as JRASERVER-1391 and JRASERVER-6851 instead of half-arsedly "fixing" the UI and making things worse and then refusing to admit what they have regressed customer behaviour and log this as a "suggestion" instead of "bug" which is exactly what this is.

See JRASERVER-74935, User need to have an option to switch on/off comment paging

Challenge: @Atlassian

Please try to upgrade this Jira instance to latest LTS v9.4. You'll really appreciate this comment feature!!!

For those in pain, I have a lifehack: when you've consumed the comments and already know what to write in response, collapse the Activity, and the button will be right there.

I'm with you on the same boat, just a customer. Not sure why some of you chose to thumb me down.

We have larger audience reporting for "Changing the default order for comments from ascending to descending", 

But the behavior is not as expected, which is affected by another Bug.

• Issue with less than 10 comments is working as expected. Showing comments in the oldest first format

• Issue with more than 10 comments is not working as expected. Showing comments in the newest first format

Please talk to real UX specialists like ProContext.de before your make further bad changes on UI! A simple eyetracking analysis had avoid this last changes to the bad. E.g. to place the newest comment in the middle of a long page, what a crazy idea!

And please remove the paging at all. In our days with high internet performance this makes no sense!