We cannot use the new search because it does not show multiple fix/affects versions at a glance. The old search displays more information. It is also not clear why it shows the versions it picks. See the difference in old view. I am most interested in the 10.0.0 Version. In the old view, I can see at a glance with 0 additional clicks :
Same list of issues in the new view. It takes 5 - 7 extra clicks to see the same information and then it covers up the information in the row below with the pop up (not shown) It is just not useful:
We are unable to switch to the new view because of this issue. It is unusable
The new search UI is awful compared to the old search UI.
Simply paging up and down is very slow and forces every result to refresh.
There is no consistency between columns where text-wrapping is concerned. Some columns such as Summary and Team do wrap when the width is narrow, but most columns do not wrap. There should either be a wrap option per column, or they should all wrap by default.
There is way too much wasted vertical space in every row. This absolutely needs to be more compact. A user must be able to see as much data and as many results as possible in order to spot patterns, commonalities, etc.
The new issue search does not allow easy searching of comments. Comments contain important information and not being able to easily search them when searching everything is extremely unhelpful.
The New Issue Navigation is useless if it doesn't search every text field.
I am able to see 6 additional columns in the old view. In the new view I have to scroll to the right, which means now I don't know which issue I'm even looking at!?! This is so much worse.
When 99% of the comments on the New Search functionality are negative, most with very detailed issues re. poor user experience, loss of functionality, poor functionality of New Search -- then how is Atlassian convincing itself that this is a good move? Will there be any response to any of these specific concerns?
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.
@Tony Marek I think there may be some selection bias at play with the "99%" negative comments. It's certainly true for this article, but most of the feedback I've heard on the issue navigator experience (across an enterprise) has been neutral to positive.
To be clear - there *are* certainly improvements that can and should be made to this experience. However, it has brought forward some positive changes and has been quite workable for my team in daily use. My company may be in the minority here, but maybe it's a silent majority?
i think that could be the case; but it could also be the case that a lot of people who don't like it don't even bother to post anything, or don't even care or know there is a forum to complain. Often, discussions to migrate to new platforms may happen, without ever reporting any issues.
I know at my organization they will complain to me, or their colleagues, but won't bother to come here. After all, they (we) all have work to do, and we can't waste all our time complaining here or beta-testing for free for Atlassian.
When people do take the extra effort to report issues, it is because reporting those issues seems worth the extra effort, so Atlassian should pay some attention to them, instead of their apparent policy of: "we are doing this because*, and you will shut up and like it".
*PS: It seems clear to me that Atlassian is not improving or refactoring old/current code, and instead replacing old code with new shiny code; that's why they need to do so much work just to catch up with pre-existing functionality and why they create new bugs that didn't exist or had already been fixed in the old code. Maintaining multiple versions of code is a pain, so they force us to use the new version so they can get rid of the old stuff and focus only on the new stuff. Just as with the new sidebar, that's a self-inflicted problem, and they should instead make incremental changes without wholly replacing the navigation with "some good things, some broken things, some missing things".
@Josh There can certainly be selection bias. This specific thread targets exactly people who did not want the new search feature. They are brought here because they have a permanent banner that tells them they can't use the old search anymore. Which means they are DIRECTED here. But this also means that you can be 99% sure that users that respond here actually interact with the feature in question.
Any threads that have responses from threading the forums that aren't forcefully directed to it would obviously be only answered by users who casually engage in the community development because they enjoy it. And that's fine. But it is normal for those feedbacks to be generally positive. However you can't know for sure that most of those responses are from users that actively engage with the issue in question (in this case, the search), let alone all its features.
Honestly most of the time people don't have time (or desire) to casually browse community forums. I certainly know no one in the company I work for does, and I don't either, except when it might start impacting our performance negatively (like right now). I've already been made keenly aware that they aren't happy with these upcoming forced changes, and I'm hoping that we can avoid extra work (whichever form that takes) by simply getting to keep the old search mode.
However most users that respond in this thread, specifically do interact with the feature in question, for CERTAIN. Because they would not be here if they didn't.
The selection bias in this case is that any "news thread" that aren't be forced upon users can be browsed by just about anyone, regardless of how much they interact with the features. In fact some might do so simply because they want the rewards of being active on the forum (for example your Rising Star tag).
However this particular thread is highly likely to be visited by users interacting with the feature in question, since they are forcefully directed to it. And it seems like the general genuine concern is being forced to downgrade our experience, for reasons we don't understand or agree with.
Again, the problem is not with the implementation of the new search. The problem is with the permanent removal of the old one. If they want to permanently stop updating and patching it, that is unfortunate, but sometimes understandable or inevitable. But it should not take that much to simply NOT remove it, and let users keep the old search mode.
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.
It's usually not practical for companies to maintain multiple versions of their UI (imagine if the UI for Windows XP, Windows 2000, or Windows 95 still needed to be available within Windows 11). Asking Atlassian to keep the old search indefinitely is likely not going to be a successful path to pursue.
Instead, I'd recommend calling out any specific missing features or improvements that are necessary for the new experience to address the biggest pain points (as many commenters in this thread have done).
The comparison with Windows OS might seem intuitive, but it isn't. If I don't like Windows 11, I can absolutely just install my old Windows XP and just stick to it. I won't get any updates. There are hundreds of security breach. Most apps won't work on it. But that is my problem, I decided to stick to it. However I can't keep the "old search" even if I want to "endure what's wrong with it" over what's new.
It's also actually quite common for softwares to maintain multiple versions of their UI, depending on their need, but that isn't the point of the discussion. We're talking about search/filter methods, that worked perfectly fine (user end), and is getting forcefully changed to a different (less efficient) layout with a degraded experience.
I can see where you're coming from for the feedback. It's true that pointing out specific missing feature would ultimately provide better criticism, but there are a few core issues with this.
1. A BIG problem with the new UI is its layout. It's just poorly thought out, and less compact and useful than the old one. Displayed information at first glance is no longer sufficient, scrolling needs to be done on the dozens (sometimes hundreds, after one returns from vacation) tickets that need to be verified. That's an issue that has no business EVER happening. I don't understand how it even came across as a good idea. Trying to provide feedback for this would be the equivalent of saying "Don't do any changes".
2. Another big problem is that the old search is a LOT easier to customize and personalize for each user, meaning that I would need to track down the specifics of the search of everyone in the company I work for (we're talking hundreds of users) -> Have them switch to the new UI -> See what is missing -> try to find if it now exists under a different form -> have them log their general problems with it -> report them all here? Again, this isn't something you can easily provide criticism for.
This type ticketing system does not pertain itself to getting personalized feedback in a large organisation. If I extrapolate from our personal (as a company) experience with it, we use it as a means to an end (which is tracking tasks with reminders, set under certain rules and etc). 95% of users in the company aren't familiar with anything about the system that isn't directly linked to their needs and task, because they don't need to be, it would be a waste of time to engage further than they already do. That doesn't exactly build a user-environment where they would provide feedback or engage in the community that is present in this forum. For most of these users it's more about "dealing with" the ticketing system to the extent that their jobs requires them to do so. If the ticketing system works for the company, then they just have to deal with what they don't like about it. If the ticketing system does not work for the company, then the company will likely change to another one, that's really as far as it goes.
Please do not force us to stop using the old search until the new search returns the same results as the old search--specifically, ensure that comments are included in the fields searched. (When I found out the hard way that the new search was broken, by not getting critical results I needed due to comments being excluded, was when I had to go hunting for a way to go back to the old search.)
If you want users to adapt to the new view you must allow us to configure and save the view, lock columns into the view, and stop refreshing every thing when scrolling. I am still searching to find what part of this is faster because this new view basically takes minutes to load over and over. I don't have time for this, and always end up switching back to the old, reliable view.
Please don't remove the old search!!! I heavily use labels and unlike the new search, the old search allows me to to see all labels for each issue in the search result. The new search only shows one label and requires me to click the + sign on each issue to see the other labels and even then I only see it in a pop up (it doesn't persist). As others have said, at least make the old search accessible even if no new enhancements are made to it.
As per usual, someone in UX design has decided to "Update" something that doesn't need to be changed, nobody asked to change it, and when it changes will remove valuable functionality. And we're stuck with a forced advertisement for the next 6 months, to boot. Do they require "User Aggravation 101" as part of CompSci degrees, now? Atlassian, Microsoft... Far too many designers ruining interfaces and functionality, all in the cause of "Progress." ...At least let us dismiss the darn message until a week before you change everything @atlassian
We hope your company can attach importance to everyone's comments. Most people in the comment section should be heavy users of Jira. Everyone hopes that Jira will get better and better. The current mandatory update in November gives most people the feeling that regardless of whether users are willing or not, this mandatory update will be implemented in a one - size - fits - all manner, even if the new functions still have not been optimized and iterated to a version that most users are satisfied with by then.
In addition, recently Confluence has also started to force the pop - up of switching to the new page. Many documents with the old page layout are difficult to open or cannot display past data completely. This is disastrous for project management and knowledge base integration.
In fact, what users comment on reflects the various deficiencies and defects of the current new functions, which affect daily work management. And the old functions can still perfectly match the needs of daily work. Personally, I still hope that the new functions can continue to be optimized and iterated. After continuously integrating all the advantages of the old functions and going through many internal tests and user experience feedback, the latest version can be released to the outside world at that time. I believe that no one will be obsessed with the old version anymore, but will invest in the use of the new version.
Finally, I have always believed that Jira and Confluence are the best version management tools. I sincerely hope that your company can pay more attention to the comment section and collect more optimization suggestions from users.
We hope your company can attach importance to everyone's comments. Most people in the comment section should be heavy users of Jira. Everyone hopes that Jira will get better and better. The current mandatory update in November gives most people the feeling that regardless of whether users are willing or not, this mandatory update will be implemented in a one - size - fits - all manner, even if the new functions still have not been optimized and iterated to a version that most users are satisfied with by then.
In addition, recently Confluence has also started to force the pop - up of switching to the new page. Many documents with the old page layout are difficult to open or cannot display past data completely. This is disastrous for project management and knowledge base integration.
In fact, what users comment on reflects the various deficiencies and defects of the current new functions, which affect daily work management. And the old functions can still perfectly match the needs of daily work. Personally, I still hope that the new functions can continue to be optimized and iterated. After continuously integrating all the advantages of the old functions and going through many internal tests and user experience feedback, the latest version can be released to the outside world at that time. I believe that no one will be obsessed with the old version anymore, but will invest in the use of the new version.
Finally, I have always believed that Jira and Confluence are the best version management tools. I sincerely hope that your company can pay more attention to the comment section and collect more optimization suggestions from users.
50 comments