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.
Thanks @Ahmud Auleear - I appreciate the response comment!
I agree with most of what you say but, personally, I do think if there was more focus on performance over UI changes like this, it would be better use of Atlassian time - though I also fully understand the crazy juggle us admins and developers have to do.
Yeah, please do share the transparency of why this is going to change and exact roll out timelines - that also helps us admins make our users aware of what is coming.
"The decision to reposition the Status field came directly from user research across various segments including new users, existing users and admins. A recurring theme in our studies was that some users, particularly those newer to Jira or business users, often overlooked or couldn't locate the status easily.
This problem was reocurring over and over again or is it recent? New UI introduced changes in font, colouring and button contrasts. Status button isn´t so well visible as it used to be.
Also from my experience users are not looking for functions they are not used to. If they are not used to some functions from their previous system they will not look for it in new one or they can be used to different placing.
I am curious how users are going to work with statuses now. When we change status we also change assignee to the next role in line. For this we have Assignee as the 1st field in details to have it as close as possible to the Status. Well we had until you moved it away.
Well... some will welcome the change, some will not. I am just super tired from the never ending UI changes and constant need of forgetting hard coded muscle memory.
This is unrelentingly awful - the change applied itself overnight on some projects and not all. This is not helpful, and in fact just causes confusion.
That is the stupidest decision I've seen in a long time... At least make that button "fixed" because now, if you scroll to the comments on a work item, the button disappears...and your supposed "easier to find and better productivity" argument becomes useless. Total nonsense...
This is really bad. Whoever came up with this idea doesn't use Jira. You have so many issues with user unfriendly configuration and everything, and you decide to MOVE THE BUTTON that had a perfect position. Right panel is action panel.
Makes ZERO sense to have this button under summary. Not to mention the fact, that it disappears when you scroll down. LMAO. So bad!
This is even a bit funny! Cool comments, so we can see that all the users who asked you 'for this kind of improvement' are 'very happy' about it :) The comments are literally overflowing with gratitude for making it very intuitive and understandable 🫠
I don't agree with the statement in this post: "What do you need to do? Nothing! This change will be applied automatically."
Uhm, actually, yes, you do need to do something: inform everyone in your org and explain over and over that Atlassian decided to change this, and there is no way to revert to the previous method ;)
| The status field was grouped with other actions, which sometimes made it tricky to find.
Actually, the status field was next to only one other Icon. Now it is part of a button group and not more/or less visible on its own.
I don't care about the change itself. What I don't understand is, why these changes are not being grouped. Why not roll it out with the big UI change?? Same thing happened with the new floating menu in Confluence. It's a nightmare for Admins and users alike.
@Ahmud Auleear I tend to agree with the opinion that moving the Status field to under the Summary will only complicate finding it. The screenshot you included is from a work item in Jira, but if you look at a work item in JSM the space under the summary field does not have the grouped apps button, instead it shows them as separate ones. And that's before you have third-party apps that adds their own buttons right there. Also, was tabs in the screen considered? If you have a screen with multiple tabs it now makes it even more crowded...
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.
some users, particularly those newer to Jira or business users, often overlooked or couldn't locate the status easily
Sure, new users, especially those who do not read the documentation, have a hard time navigating a complex product. But: The solution isn’t dumbing down the product, but educating that new users.
Thank you all for taking the time to share such thoughtful, passionate, and detailed feedback. I hear the concerns, the frustrations, and the fatigue many of you are feeling.
Maybe you hear it, but still you decide to ignore it. All comments in this post tell you that this is a change that nobody likes or wants. Your reaction? “Thanks, but I do not care. And by the way, there’s more to come”. Well, that happens when a company becomes big enough to lose contact to its core users. Now we have another Asana, but with a much worse UI. You already have Trello that can’t catch up with Asana feature wise - and your reaction is to downgrade Jira? Smart move.
I'm really disappointed in this change; Status having its own spot above the action panel made a lot of sense and moving it to a far more 'busy' area (like under the Summary field)... I just don't see it achieving the goal you are hoping for here. If you want something to be more visible and more easy to find, draw the eye to it with emphasis or colour. It feels like you're placing it somewhere the eye already drifts over.
Considering the large amount of significant UX changes that have been introduced in the past year, I think change fatigue is also a very real factor for our users.
@Ahmud Auleear - could you also provide some clarity on what you mean when you say this will be rolled out starting mid-August? Will this change come through as part of a Bundled release (for those of us who utilise that function) or will it just appear in our Projects one day?
Dear @Ahmud Auleear , Do you have any date on your mind when this update is planned? Since it's September, but no additional information about this. I'm asking because we need to inform users in our company beforehand and would be good to understand when we should plan this. Thank you in advance for the response.
This change means more scrolling for our teams. Could we at least make the ticket description and status fixed at the top while scrolling for lengthy tickets/work items? As we are reviewing items with longer details and updating comments, we have to scroll down to review all content, comments, etc., then scroll up, up and up again to get the the top to change status. For our teams this is not an improvement. I'm struggling to know why status was hard to find previously (top right, in fixed position).
I completly disagree with this change. Who exactly did you talk to before making this change? We often have to scroll down into an issue to see comments, and now we can no longer see the status as it is hidden at the top of the issue! The whole point of a details sidebar is to see the details of the issue. Status is a critical detail, and now it is hidden at the top of the issue.
If you are going to make major changes like this, at least plan for a way to let users go back.
And by the way, I never recieved notice of this change - we just suddenly saw go live in our instance!
Please listen to your customers - we have been using Jira for 20 years, we should be at least consulted on changes.
(This post was edited to remove profanities and exclamation points)
Could you stop making continuous changes to the features without giving users any options? Lately, you have been making a lot of modifications that worsen the user experience and never give users the chance to make choices
This is not working for us, now you're scrolling down the page and you no longer have access to the button, but you have to scroll up to the top again. The button was previously pinned to an absolute location on the page due to its residency in the details side-panel and scrolling the main contents didn't have any effect on the location of the button, it was easy accessible all the time. Especially because you always knew the button was just an inch away from the right side of the window. Now this (very important!) button is somewhere hiding in the grand scheme of the content, moving back and forth when you pin or unpin the navigation bar, etc.
If there is a ticket with lots of information in the description or additional custom fields... I now have to scroll all the way back to the top to change the status. Typically someone will say something in the comments like, OK to close, or please move to testings.... NOW I have to go back to the top of the page to change that.
This is NOT easier or faster.
Give people the option to put it where they want... don't force the change on them. Moving UI elements around that no one asks for just frustrates them.
@Oleg_Chaichuk you can vote here. I had this feature request created.
The decision to reposition the Status field came directly from user research across various segments including new users, existing users and admins. A recurring theme in our studies was that some users, particularly those newer to Jira or business users, often overlooked or couldn't locate the status easily.
This doesn't make any sense, of course new users are going to be unfamiliar with the interface. Who thought it was a good idea to sacrifice the existing users with years of muscle memory over new users?
On a 4K screen, the move is especially egregious because of how far the dropdown is from other actions you would normally do when changing the status, like changing the assignee or priority.
I'm getting dozens of complaints because this was applied overnight with no warning and no way to appease users other than telling them to get used to it.
Please undo this change. Now you have scroll back up in order to update the status you looking at the comments or description. Also it inconstant. On Service tickets the Status in the Context and also when you pop up the window it in the Context it only seems to be under the description when you open the ticket in its own tab.
52 comments