Thank you for the update and for acknowledging the impact.
For our workflow, the most important part is not just having more space for the work item. It is the old split-view experience itself: a persistent list on the left, a large work item view on the right, and the ability to move through items without losing visual context.
A modal may help with screen space, but it is not necessarily an equivalent replacement if it covers the list or interrupts the triage flow. The previous Detail View worked well because the list and the item stayed visible at the same time.
Our preferred solution would be to restore the old Detail View behavior, or provide it as an option, at least until the new modal and navigation experience fully matches that workflow.
Thank you for the update and for acknowledging the impact.
For our workflow, the most important part is not just having more space for the work item. It is the old split-view experience itself: a persistent list on the left, a large work item view on the right, and the ability to move through items without losing visual context.
A modal may help with screen space, but it is not necessarily an equivalent replacement if it covers the list or interrupts the triage flow. The previous Detail View worked well because the list and the item stayed visible at the same time.
Our preferred solution would be to restore the old Detail View behavior, or provide it as an option, at least until the new modal and navigation experience fully matches that workflow.
My thought, based on the feedback here and elsewhere, is that the overall VOC consensus is to keep as-was or at least the option to continue using as-was.
Perhaps it is reasonable to offer reasoning around why as-was, or view switching is no longer viable.
It would also be cool to know the audience and VOC for the requirement of the current spreadsheet type view. I'd like to gently point out that Atlassian do not owe any explanation, but setting context may perhaps help soften our current pain point.
I don't understand why is Atlassian making these changes just to change something. I don't see any benefit for my team. All i receive from users is only confusion, because something what has been possible to set as we wish, is now removed. If this would be as third option to already existing list view and detail view it would be totally fine and nice to have. Now we have view which is useless and no possibility to switch back. I'm slowly getting tired about this unexpected UI changes.
@Amanda Sacks I suppose your post from yesterday should be comforting, that Atlassian is moving forward with new changes to address this misstep. Perhaps it is, to a degree. What would be far more comforting, and likely better received by the user community, would be a response along the lines of: "First off, we're sorry. We removed something that mattered to your daily workflows... before we'd shipped a proper replacement. That's on us... We're rolling back that change right away and will pause to consider how we can chart a better path forward which retains the important feature you need."
From where I sit, Atlassian is embracing the modern "fail forward" fallacy; the thinking that reversing course is always bad and continuing forward is always good. I see this as a case where Atlassian should reverse this change, pause to reflect, and then resume forward progress on a different course.
Thank you for listening to the feedback, and starting to take corrective action.
I would strongly ask that you please consider bringing the toggle button back, and add a 3rd option to it with your new view, or something equivalent. You can even hide it under the three dots '...' and default it to your new view, and I think everyone would be happy.
This would give everyone some grace period to transition to the new view, and give you metrics on adoption rate of the new view vs old views. If your goal is to eventually remove the old 2 views, this would also give your team breathing room to reach feature parity of the old views, before phasing out the toggle. Right now it feels like you are flailing and scrambling to throw on an improvement to help fix peoples broken workflows. This just seems like a bandaid and only partially address some of the problems, other people still have other workflows and views they used as comments indicate.
A good example of this approach done successfully, in my opinion, is the new Bulk Update UI on the filter issue screen. This is an improvmenet in many ways, but they didn't remove the old bulk-update multi-screen workflow, as every feature wasn't there yet. This gives them time to reach feature parity, lets me as the user slowly acclimate and use the new UI more, and can fall back on the old bulk-update if something is not working.
And a note on your 'seasonal releases'. the problem here isn't your release schedule, the problem is you made a breaking workflow change, no amount of notice or timing would fix this problem. A graceful transition period where we can fallback on the old method, with in-UI pop-ups or announcement banners near the new feature would help (not everyone follows Atlassian release notes, blogs, posts, etc.).
Thank you for acknowledging the impact this change has had and for pausing the rollout for additional users. I appreciate the transparency and the willingness to listen to feedback, but those of us who have already received the update are still left without the workflow we've relied on.
I still hope you'll consider restoring Detail View as an option rather than replacing it entirely with a modal, which would not be an ideal solution, at least for my team. The issue isn't just screen space. It's that Detail View supported a workflow that many of us depend on. If the preview panel and modal work better for some users, that's great, but they shouldn't come at the expense of removing an existing workflow. Different users have different screen layouts, accessibility needs, and ways of working. Offering both the new experience and the previous Detail View would give users the flexibility to choose the interface that best supports their productivity.
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 Champions.
I am guessing that there is some technical load that Atlassian was trying to address with the preview panels but I would think that they could have done that without negatively impacting users the way they did. I know there is a lot of technical debt/baggage in the legacy code but hopefully after a second gigantic debacle with major UI changes in about 12 months maybe they will have actually learned a lesson from this one and proceed with more caution in the future.
"a more convenient and efficient experience" is in the eye of the beholder, I guess. I definitely prefer the previous interface. OK, I get that you want to change the default interface, but I can't believe there's not an option to toggle back to the previous interface. Please let me toggle back to the older interface.
After reading more of the feedback in this thread, I think this is clearly not just an issue for one team or one workflow. The same themes keep coming up from different users: the old Detail View was useful because it gave people choice, preserved context, and supported fast review of work items without forcing a modal or a narrow side panel.
We appreciate that the rollout was paused, but for customers who already received the change, the disruption is still there. Also, quite some time has now passed since this was first raised, and so far we only have written updates, with no visible rollback option or concrete replacement available to affected users.
A modal and navigation arrows may help, but they still sound like a new workaround rather than restoring the workflow that was removed.
Could Atlassian please consider restoring the previous Detail View as an option, either as a user preference or admin-controlled setting, while the new preview panel/modal experience is being improved?
This would address the immediate disruption without blocking the new direction. Users who prefer the preview panel can keep using it, while teams who depend on the old Detail View can continue working effectively.
In short: please give users the choice back as soon as possible.
@Arvin Bryan San Pedro Gaw and that's how many of us work... just we want most of the screen for B, because we are mostly interested in what the card says, and any comments at the bottom. Already know what I've got from the list in A, I don't need anything more than just a simple list of the cards. We change status in the detail view not on the left side when we are done. That's how I operate. So while it's great for you, it's not great for us. Status lists are useless, I already filter mine by what I need to see before I even reach this screen.
@Arvin Bryan San Pedro Gaw I'm really happy for you that it works, but it doesn't work for the VAST majority of people. I don't think anyone here cares that there's another OPTION for folks like yourself who work this way, but it should be a CHOICE. Atlassian took that away from us and made most of us worse off for it.
I would prefer that this be an option that can be toggled on and off. We use full screen views of a filtered list in order to do triages with groups of individuals. This is horribly inefficient with the side panel, does not work well with small screens, and hot keys can be inadvertently pressed while on the list and it will affect the ticket in the split screen.
118 comments