Is there an update on when this will be released? We're trying to launch a project with a business team and I was surprised by the similarities (and ultimately differences) between the two lists. I agree, it's confusing for business teams why some features work on one and not the other. Or why one can be set as a default view and not the other etc.
Hi there, I'm wondering if there's a way to trigger the bulk-change interface from the new List / All Work view. When selecting items here it seems like I can only Delete or "Edit Fields" but my use-case was needing to migrate issues to a different type (ie. sub-task to story).
Will this have the ability to save column layouts with a filter so that users can have a consistent view experience when opening another user's filter?
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.
Q: Why can’t I drag-and-drop to reorder when grouping or filtering? Drag-to-rank only works when sorting by “Rank.” Grouping and certain filters override the ranking sort order, which disables drag-and-drop for now.
The Drag-to-rank feature currently available in our All Work tab doesn't work by default. To see this, go to All Work, and if a Filter is enabled then use "Filter > Clear all". Now try Drag-to-rank. It won't work.
This is because the default All Work filter uses "ORDER BY created DESC". To see this, use "Filter > JQL" with the Filter cleared. This seems wrong, particularly when the Board Filter uses "Order by Rank"!
I would strongly recommend that the "All work" tab use the Board Filter by default, to ensure that:
the work items in "All work" are ranked like users see in the Backlog on their Board; and
the Drag-to-rank feature will work by default (assuming the Board Filter follows the best practice of ending with "order by Rank").
That makes more sense than some arbitrary sort order.
It looks like something has changed in the All Work interface for me. It seems a little cumbersome to get to the JQL option.
The buttons to switch from Basic to JQL to Advanced are sort of "hidden" under the filter button. I thin they should be brought forward and maybe put next to the Search box.
Can I please know why inline editing is not available for some custom fields? Also, the custom field people picker used to show people's avatars - now it is replaced by text - is there a plan to bring this feature across from the old list to the new?
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.
Hi @Tanya Maddalena - Please can you provide an update for us? I think 6 or 7 months ago you said it is rolling out over the next few months? Is there anything holding this up?
Also for the Hierarchy update, does it allow for as many levels as configured? Eg we have Initiative > Epic > Task > Sub-task
I am also in agreement with @James Woyciesjes comment above RE finding the JQL. The Basic|JQL switch works much better
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.
This change seems to have just rolled out for us, and especially the removal of the master-detail view from the list kills productivity of our QA folks who have a workflow of quickly scanning through a list of issues without having to fully open them. At the current state, the list still takes up half the screen and this leaves very little room for the issue details.
It also seems like the list is now always auto-refreshing on changes, whereas previously it only refreshed on demand. Especially for filters that e.g. rely on the last update timestamp this make working with the list inconsistent as it constantly reorders when work items are changed. I.e. you can't no longer just go from top of the list through everything to the bottom of the list, check it, progress it, then continue with the next, because you have to re-focus on what the "next" ticket then is that you have to check.
66 comments