Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Many of you have quite eloquently raised concerns about how this UX change was selected, validated, verified, communicated, released, and the resulting impacts to your teams. I agree with most of what has been described. I want to draw your attention to a related thing I noticed...
A week and a-half ago, a suggestion was created in JAC to make this UX Status change configurable. And, it was recently updated to include some community-offered ideas about impacts.
Please note well: as soon as the suggestion was created, all comments were disabled. One could vote for or watch the item, but not comment on how to improve the suggestion. In many years of using Atlassian products and JAC, I have never seen comments disabled for a suggestion or defect. My hypothesis is the Atlassian team acknowledges the challenges from this UX change, and either: did not want diluted feedback between platforms (the community vs. JAC), put it in a project where comments are not permissible, or did not want any customer feedback on their additional changes.
I have seen this symptom before, where I suggested something in JAC, and then others have re-written my suggestion into a completely different thing. Fortunately, I was able to comment and try to course correct back. But when comments are prevented, that is not possible.
Respectfully, I encourage two things:
even though we cannot comment on it, vote for and watch JSWCLOUD-27789
if you have submitted any defects or suggestions to JAC, review them to confirm they still match your concern / intent, and contact Atlassian Support if they have been altered to clarify why
Kind regards, Bill
UPDATE: The above noted suggestion was moved to a different JAC project and commenting is now possible. Please find it here:
This does not make sense. You took the button from in your face to highlight action to a cluttered corner below summary where I have to play gymnastics to do the one action I need to be done.
Designers are wrong on this, and perhaps you should review your A/B testing process. More importantly Atlassian needs to work on communication. This is such a significant change that at least on the face seems like no one asked for.
Huh. While it's not perfect, poking around on the new JAC (huh, does anyone know when they finally migrated to the Cloud? I'd love to read the retrospective on that), I discovered that opening an issue from within a Filter provides a view where Status is pinned to the top of the screen. Check it out:
While that's not putting Status back where everyone expects/wants it (except apparently new users/Business users/users who never have more than 1 comment on their issues), I guess it's an improvement/compromise.
So MAYBE Atlassian could implement this for REGULAR Issue View?
WHOOOPS, because of font/UI changes, I got fooled into thinking that jira.atlassian.com (aka JAC) is on Jira Cloud, but when you look under the covers, nope, still Data Center:
Remove the lock and allow Admins to move the field to location that works best for us. The scrolling required to go BACK UP after adding comments is a much WORSE experience.
This change is so unbelievably bad and unnecessary. The productivity hit alone with this change is going to be huge. As others have said, change fatigue is hitting hard about now, and many of these changes, such as the sidebar and how we access projects and filters, have been productivity hits rather than improvements. Please address the issues that power users and administrators have been filing and voting for over 10 years. In my 20+ years using Jira I don't think I have once heard wow it would make a lot of sense to relocate the most used button in Jira over to a non-sensical location like you did.
Every one of my users in my company has complained about this change. We have complex workflows, and use comments heavily. Its not uncommon to see literally hundreds of comments on an issue back and forth.
Each one of those requires someone to enter a comment, then scroll WAAAAAAY back up to the top of the page, to update the status.... So much scrolling.
The recent changes are unacceptable and demonstrate a complete disregard for efficiency. The status updates are poorly executed, and the revisions to the admin portal have made tasks exponentially more cumbersome rather than improving them. This level of decision-making reflects a serious lapse in judgment. The team responsible for these updates has failed to meet even the most basic expectations of competence. The Entire team should be fired.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Hi @Susan Hauth _Jira Queen_ -- Comment-disabling on that specific suggestion seems to be intentional as doing so for other items still works when one is logged into JAC.
@Carrie J i just voted on it a few minutes ago. look for the "More" dropdown to the left of the status dropdown (under the title). i think i had to fresh my page a few times before i saw it
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
- Vote and watch JSWCLOUD-27789. As Bill points out, comments are disabled (which is a first as far as I can remember) but vote and watch. Atlassian doesn't typically care how many folks have voted as a rule, but it's hard to ignore the nearly 700 votes in less than a month.
- If you have a CSM, reach out and bother them. Call it payback for all of the ads they're inserting into the platform.
- Put in a Support ticket and ask them to disable the change. If nothing else, the number of support tickets is another metric, but there are times when they can undo some of these changes even when initially they say they can't.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
The move of status from the right panel to the left panel was jarring and horrible. Real world work items have pages and pages of description and comments. On the laptop, I can no longer just glance to the top right and see the status.
I understand status is now easier to find on a narrow display mobile device. But it's now harder to see on a laptop.
Please, please! Do NOT increase the non-scrolling header to keep the status visible. That would lessen the scrollable space. I need as much scrollable space as I can get to actually work on the work item.
We had to endure the huge non-scrolling comment footer for a long time. I was very glad Atlassian modified that comment box to be non-scrolling when viewing the comments section. (Although, they made adding or editing a longer comment a crappy experience.)
I’ve been able to adjust to most Jira changes, but I was initially concerned when I couldn’t locate the Status switcher as it seemed like it might have been removed. Several teammates experienced the same issue. Since our team often has longer descriptions and extensive comment threads, we frequently need to scroll. Having to return all the way to the top of the page to update the Status has become a significant inconvenience.
I understand from earlier comments that the current design is based on UX research and feedback from the broader user community, and that our use case may be less common. That said, I’d like to know where I can submit a request to enhance the page layout so that the Summary and Status selector remain visible at the top of the view. This would make it easier to quickly see both the Summary and the current Status while working in longer tickets, and it would address both a longstanding usability gap and the new challenge introduced by the recent changes.
276 comments