Feedback Issue: Planning Views (Work items list + Saved Views)

Welcome to the Planning Views GA Feedback Issue! 🚀

The purpose of this feedback issue is to collect your experiences with Planning Views. Our goal is to understand how Planning Views are helping (or hindering) your planning workflows, identify bugs and improvement areas, and prioritize enhancements based on real usage. Your feedback will directly influence how we evolve Planning Views post-GA.

Why we made this change

If you're looking for more context on why we made this change and where we're headed, we've published a blog post that walks through the thinking behind Work Items, Saved Views, and what's coming next:

https://about.gitlab.com/blog/agile-planning-gets-a-boost-from-new-features-in-gitlab-18-10/

The short version is that work items is the foundation for a unified planning experience, one where you'll eventually be able to configure your own work item types and names to match your team's hierarchy.

What you can expect from us

1. We will read all feedback
2. We will prioritize fixes for based on feedback patterns
3. We will create issues for reproducible problems with severity/priority labels nested under this Epic
4. We will reach out for clarification on complex feedback

Feedback threads

• Thread 1: Suggestion to link Feedback Issue in onboarding experience
• Thread 2: Ask for default Epic/Issue views and an OR operator
• Thread 3: Bug regarding items ordering in the All Items tab
• Thread 4: Challenges/confusion around UX
• Thread 5: Pushback against new approach and change from Issues and Epic views.
• Thread 6: Ask to return to old Issues/Epics view. Slower productivity with new approach
• Thread 7: Like new view but found a potential bug with applying filters.
• Thread 8: Burdensome creating Private Views for each and every project. Would like them to carry over.
• Thread 9: Pushback against new approach and concern over confusion potential.
• Thread 10: Similar feedback to thread 9.
• Thread 11: Question around rollout plan
• Thread 12: Confusion around UX
• Thread 13: Description removed when switching types
• Thread 14: Miss seeing a count of Issues
• Thread 15: Prefer Issues to Work Items terminology
• Thread 16: Change breaks browser bookmarks
• Thread 17: Confusion around the change.
• Thread 18: Asking for change in default sort order, missing Closed Issue view, don't want to create views for all projects, when using Browse views expect to see existing view from other projects or groups.
• Thread 19: Feedback that change is creating more complexity in the system then necessary.
• Thread 20: Feedback that they are not liking the change and that it makes it hard to find the thing you are looking for.
• Thread 21: Providing PM context on why behind change.
• Thread 22: Feedback that folks will struggle to report problems now because of confusion with Work Items naming and that the new editor is challenging to use.
• Thread 23: Don't like the new flow and how it requires creation of Open/Closed views in each space.
• Thread 24: Likes new capabilities. Has a request related to state and wanting created items not to default to the last item created.
• Thread 25: Feedback that they dislike the new experience.
• Thread 26: Misses the direct access to Open and Closed and that they have to use a filter.
• Thread 27: Confusion over Saved Views functionality.
• Thread 28: Feedback that it would be nice to designate some views as default and public. Not a huge fan of the Work Items terminology.
• Thread 29: Like Saved Views and being able to share with their team, dislike that old numbering is gone and that Issues/Epics were renamed.
• Thread 30: General feedback over internal facing Product Planning views.
• Thread 31: Confusion over setup of Saved Views
• Thread 32: Suggestion to rename Work Items to Bug Tracker
• Thread 33: Request to categorize work items by Epics
• Thread 34: UX on Brave browser not rendering cleanly
• Thread 35: Feedback that items are showing up in a saved view that shouldn't be included.
• Thread 36: Missing standard tabes for Open/Closed.
• Thread 37: Missing count of Issues
• Thread 38: Desire for standard Open/Closed views.
• Thread 39: Desire to go back to previous experience
• Thread 40: Desire to go back to previous experience
• Thread 41: Desire to Issues to be naming instead of work items and a counter
• Thread 42: Expressed desire for previous experience and need for stability in the UX
• Thread 43: Suggestions to have a nested list of views underneath the Work items list in the sidebar
• Thread 44: Feel this is a regression
• Thread 45: Desire to go back to previous experience
• Thread 46: Looking for a better understanding of the Work Items vision and where things land on a Project/Group level
• Thread 47: Missing count of work items
• Thread 48: Finding the new Saved Views experience challenging to use.
• Thread 49: Don't like new UI
• Thread 50: Don't like new experience
• Thread 51: Would be nice if at Group level to have insights into Projects underneath
• Thread 52: Doesn't understand the differences between current objects. Believes they should all be one object type
• Thread 53: Doesn't like new experience and would like to go back to old.
• Thread 54: Doesn't feel work items is ready to be rolled out. Asked for a rollback to previous experience to be considered.
• Thread 55: Feel the change is very disruptive.
• Thread 56: Hard to report bugs with the work items language
• Thread 57: Created extension to mirror previous experience.
• Thread 58: Ask to filter by assignment dates
• Thread 59: Desire to return to previous experience
• Thread 60: Bug list seems to be cached and want to switch to the old experience
• Thread 61: Found a bug in the label page
• Thread 62: Would like more space to create items on the work items creation page
• Thread 63: Feel the old experience was better and didn't need to change
• Thread 64: Find work items naming confusing. Missing closed issues and numbering of objects. Feel the new editor is too small and want to go back to previous experience.
• Thread 65: Ask for filter of assignee to current user
• Thread 66: Desire for old experience and feel new is overcomplicated
• Thread 67: Providing way to go back to old experience
• Thread 68: Desire for nested objects in saved views
• Thread 69: Renaming to work items makes reporting bugs challenging and GitLab harder to navigate.
• Thread 70: Not a fan of GitLab UI changing so frequently.
• Thread 71: Miss Issue count and Open and Closed default. Feel the rollout was poor.
• Thread 72: Miss Open/Closed/All buttons and having challenges with saved views
• Thread 73: Miss numbers of Issues
• Thread 74: Post about blog from Matthew
• Thread 75: Not enjoying new experience and had to spend significant time configuring it.
• Thread 76: Request for weight to be adding to work items at the top next to the count of work items.
• Thread 77: Customer feeling that change disrupted workflows.
• Thread 78: Customer not liking change and having performance issues. Considering moving off of GitLab as a result.
• Thread 79: Facing challenges with tokenized search
• Thread 80: Confusion over work items and issues naming
• Thread 81: Challenging to delineate between different work item types. Miss Epics views. Suggest getting rid of tasks all together. Make it possible to create issues at the root of the group.
• Thread 82: Feel the rollout is not ready for product yet and wish there was a chance to use the old functionality until it matures.
• Thread 83: Request for more available states
• Thread 84: Request to be able to create labels from the list view
• Thread 85: Bug on manual filtering
• Thread 86: Request for bulk editing of work item type
• Thread 87: Concerns over performance being impacted by the change
• Thread 88: Does not like new experience and that there is not a rollback option available
• Thread 89: Does not like new release
• Thread 90: Feels the UI is a bit messier than GitHubs but overall finds it fine and easy to use
• Thread 91: Asking for visual counter of items to be re-implemented
• Thread 92: Doesn't like the new experience and having to create new views and that label filters have changed
• Thread 93: Likes the flexibility the change gives but not work items naming. Challenges creating the right views with the existing tokenized filtering.
• Thread 94: Feel the site is a mess now and struggling to locate important work
• Thread 95: Misses the simplicity prior to the change. Asked for a revert
• Thread 96: Doesn't understand the problem this is trying to solve
• Thread 97: Various pieces of feedback regarding the new experience and how it fell flat.
• Thread 98: Question around why we couldn't toggle the old experience on and why that wasn't considered
• Thread 99: Confusion caused by renaming of Issues to Work Items
• Thread 100: Ask for adding the ounter back in and a default Open/Closed view
• Thread 101: Likes the new configurable views and being able to share with team. Would like to have similar support for MRs and Issue boards.
• Thread 102: Request for more status filters in the tokenized search bard
• Thread 103: Don't like new UX and creating saved views is very challenging.
• Thread 104: Issue with new UX
• Thread 105: Not in favor of new UX
• Thread 106: Feedback around usability
• Thread 107: Challenges with new UX
• Thread 108: Opposed to Work Items name change in particular.
• Thread 109: UX feels degraded by change
• Thread 110: Adjustment to Work Items from Issues has disrupted previous workflow.
• Thread 111: Feedback regarding new UX and filtering