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.
In the new issue search view, not all field are available and some features are hidden, like bulk operations or Excel Exports. So, a "Switch to the old issue search" feature ist available to switch back.
But this feature is not available to all users, even if permissions seemed to be equal.
Is there any dependency on browsers or operating systems?
E.g. Mac + Safari: feature is shown, Windows + Chrome: feature not available?
Atlassian Team members are employees working across the company in a wide variety of roles.
March 13, 2024 edited
Hey folks,
Thanks for actively contributing to this post with your ideas and feedback. Your comments have helped us tremendously in prioritizing and shipping the features you need. We’re excited to announce that we’ve recently rolled out a few features to improve the new issue search experience and we’ll be moving all our users into this experience soon. I’ve updated the post to include more details about these changes.
We encourage you to try out these features and continue sharing your thoughts.
Thanks for the update. I see there is an update in regards to exporting, but I don't see any mention of the exporting limit being changed. Last year I expressed concern that this new search does not have the "Export to Excel" button (see comment link below), which was the only way for my users to get around the 1,000 issue export limit easily. Is it still true this button is not available in the new search and/or has the seemingly arbitrary 1,000 issue export limit been removed in the latest update of the new search?
Is the plan to remove access to the old search by the end of March as well? If so, that leaves us very little time to plan ahead for this change. We run a lot of reporting outside of Jira that relies on being able to export a lot of issues at one time. If this capability is removed in the coming weeks, that simply doesn't leave us enough time to find an alternative solution and we'll be put in a very difficult situation.
Our entire organization was just forced into the new view. Which is FUN, because our entire workflow depends on Assets objects and fields, which as far as we can see are still unsupported; we can make filters based on Assets fields, but we can't see the content in the list of results, we cannot add Assets fields to the Columns.
Any plans to enable Assets field to the new view?
We can still manually go back to the old view, but, for how long?
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.
@Kevin Yu Starting to use this more. Please advise if we can configure the number of issues shown by default? ie. it shows 50 paginated - can we configure that? I looked at System > User preferences and i have that set to 200 but that is not respected in display here ...
I know that it may affect performance but wondering if this is possible?
Also another thing I like is that the Sprint column only shows the current sprint it is in and + button whereas the old/global issue navigator shows them all. Nice!
Eagerly awaiting the new updates to this. Thank you
Why does the total now show at bottom rather than top? It is rubbish scrolling down a screen that is mega slow rather than showing at top which is helpful.
Again why cant we chose what we want rather than force something that does not work for everyone?
Typical atlassian - we would prefer bulk clone as standard not forced to pay!
@Kevin Yu -- why is it so hard for Atlassian to let users configure JIRA functionality the way they want it?
Our organization ported over from another product to JIRA and it took us MONTHS to train and convince our business users that this was a better approach. We've created workflows and procedures based around how JIRA worked when we started to use it.
But once again, JIRA changes something that ruins my efforts to keep the business users placated with the functionalities. The old search wasn't great, but we had all of our columns within the width of a page; now we have to scroll way to the right because the columns are now huge, only using word-wrap after a much wider column width than it used to have. We recently had our items spill over to a second page (which my users hated), but with this change, we now have over 5 pages to click through to see the whole list.
It was really hard to get everyone to use JIRA the way it was; now it will be impossible.
The way Atlassian changes JIRA so drastically and so often, forcing their changes on the cloud adopters, I need to hire a full time JIRA consultant to help us change our processes.
The old search used to show the total number of issues in the search at the top. Now it's at the bottom, forcing me to scroll down to show the total. Also, some of the columns are VERY wide, forcing other columns off to the right, again causing a scroll that I didn't have to do. I wonder if these are configurations?
I haven't played with this much, and I imagine there are features I will like/need; but the change in font in the search window is awful, the column spacing in the list view of the results is too large! Where I can view all the column data on a single page (without scrolling right) that I need, now I have to scroll right and I hate it. :(
Having more dynamic search capabilities is great, but not every change is a good thing. LEAVE THE OLD VIEW/SEARCH. I have a lot of data to view in List view and I don't want to have to scroll. OR, please change the font of the result data returned, put that green checkmark back and the count of returned results at the top where I don't have to ... scroll down.
@Kevin Yu the initial feedback from both our users and Jira admins has been very positive thus far.
One thing we didn't see listed in any of the announcements is that the "Assign" action is no longer present in the ... menu.
Is this a feature or a bug? Have any other options been removed?
P.S. I was going to upload a screenshot but it appears that the image upload functionality here is currently broken. Instead of an "attach" or "done" button, it shows "li.media.uploader-dialog.buttons.done" and doesn't attach the file.
The new search is neat, but please fix the column widths, or let us adjust them manually. Having all my filter views explode horizontally so that I now have to scroll to the right in order to see columns that used to fit on one page is infuriating. I have switched back to the old search for now.
The column widths are way to wide now - is there a possibiltiy to adjust the column width manually? For our work it is necessary to have the filter results on one page, without scrolling right. It is very confusing now. We will switch back to the old search.
We have complex searches and do not expect to have to use additional tools because you have changed something that is not helpful to all.
Can we stay with current functionality as there are many issues for us inlcuding page taking almost 1 minute to load.
I dont know why you increase sizing so we have to scroll as nor helpful at all and getting to be like the kanban board that is becoming unusable with all the items we dont need displayed.
No wonder pages take an age to load or get errors.
Our accessibility team have commented that the changes are not good for accessibility and like others we may have to look elsewhere as it seems that only narratives you agree with are changed while the rest of us are left with a system that is no longer operational
I like new Issue View in general, but will highly appriciate if JSWCLOUD-26584 will be implemented. Labels are widely used in our workflow and it's important to see them all in Issue View.
There are some things I really quite like about the new search / view, however there are some things I really struggle with as well.
1) I'm really continually irritated by the Type column being so much wider, and unable to be resized. Previously, Type was indicated with T, and was the narrowed column. Now, I lost a bit of real estate because of the much wider column.
2) The inability to resize any columns is quite rough, not just Type.
3) Reordering columns is MUCH improved. Thank you!
I would love love love if there was a way to preset the fields that are shown in a basic search. I very often (nearly every time) search by a custom field. I've worked around this by isntead creating a custom search engine for my browser, so I can start from that field, but I'd love if some more common fields were able to be 'pinned' as a default filter, and I could 'unpin' some of the default filters. Example: I almost never search by status any longer but instead by status category. I hardly ever search by assignee but very often by reporter.
It's in the ellipse menu (...) in the upper-right-hand corner of the filter (where you can initiate a bulk edit from the filter). The bottom option will allow you to switch to the old view if you have the new view enabled, and vice-versa.
Note though (and JIRA will remind you if you try to switch it), that it's temporary; Atlassian will allegedly switch you back to the new view at some point. My hope is that they fix the new view before enforcing that though.
The new issue search always truncates the Labels list, no matter how wide the column is. You can only see one label; if there are others, it just displays "+n". You can click this for a specific issue to see the rest of the labels for that one issue.
I want to be able to skim through a list of issues by looking at their labels, and I can't do that with the new search page.
73 comments