It's nice willing to improve the UI but honestly making that CRITICAL action button not visible once scrolled down is so ... terrible (I don't wanna sound impolite)
If you really wanna keep it at the top left, then please make the header fixed (like we would do with the first line of a table in Excel)
Or maybe admit you have shares in mouse making companies, and a will to make people break their mouse faster by over scrolling for nothing ... ;)
Please, kindly provide the the results of the tests and the testing parameters - show your work on this one. Everybody here is against the new change is curious how the decision was made. If we have the test results, maybe there is a chance to convince us that this is the right move.
Fire the team that was involved in any process related to this change. It has caused havoc in our organization. Users are not changing the status as they cannot find the button to do it. They are creating internal tickets to report issues with Jira.
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.
Beyond the fact that this change is horrendous for all the reasons mentioned in the 8 pages of comments above...
I just found out about this change after it was rolled out to my product. I follow Atlassian's updates as closely as I can and I didn't see this announcement at all. This kind of change needs to be communicated much more directly and clearly.
I want to echo many of the thoughts already expressed in this thread. The new sidebar UI and associated design changes felt somewhat thought-out to me, but this change was very poorly thought out!
The fact that you conducted A/B testing indicates that you have the ability to offer both options. Why not simply provide companies with the choice to display their status either in the context menu or within the main content? We’ve encountered several user complaints about ‘lost permission’ or ‘unable to transition tickets’ because they couldn’t locate the new status location. Despite your claim that it’s easier to find, the context is always visible and is where people know to look, whereas the summary section is not, particularly in larger tickets.
Some other poorly thought out changes rolled out to us this week that are confusing users.
While not directly related to this specific change, someone at Atlassian decided to make forms appear in a warning yellow colour when viewed in tickets. I don’t understand the benefit of this, except that it now looks like something has gone wrong. It also makes it significantly more difficult to quickly parse the status of a form because, instead of blue, green, and red against a white background, it’s against a yellow one.
The board view in projects is now also useless. It’s fair enough if some people want to see the statuses from every single work type at once, but please make it an option, not an enforced view! We have projects with five or more work types, and different users look at the board for each. Now, they all see all the statuses, half of which they can’t even access tickets for, so it’s just blank. Again, if you did A/B testing, you know you can have it both ways. Give people the option!
Atlassian is too large to be creating a one-size-fits-all product and implementing sweeping changes like this. The costs to IT departments and workflow disruption are too significant.
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.
Alas, we find this alteration to be most…aggravating...for lack of a politer expression.
I shall prevent myself from repeating the precise exclamations my team unleashed upon discovering this change, for to do so would surely have the Almighty Himself dispatch me to the inferno before I’d taken another sip of my tea.
Suffice it to say, the entire change is both frightfully unbecoming and staggeringly inept, as if the children themselves were behind it.
At this juncture, it would be altogether more sensible to permit administrators to shape the interface to their requirements, rather than subject us to these incessant and ill-advised meddles. Good heavens, must one endure perpetual chaos in the name of progress?
185 comments