| Thanks for your feedback. Requests are triaged using automation and AI, and responsible teams include the reviews in their planning. [0] Issues (and related MRs) are targeting milestones. Since we at GitLab work in iterations and smaller changes to release features faster, epics help plan and group the issues. Roadmaps and boards are used by product managers, too. [1] [2] Example roadmap filtered by the CI section [3] Every stage, group, feature has labels applied, which allows the creation of specific filters. For example, "Category:Code Suggestions" as label filter [4] Additional helpers are available in the handbook, for example the "Features by group" overview [5] which shows the feature maintainers in the section, stage, group, product and engineering managers, etc. Customers can open support tickets, too. [6] Opening a public issue is encouraged so other community members can engage and collaborate. Often, a workaround or fast solution is unveiled because of collaboration and transparency. When in doubt whether it is a bug or feature, or asking for (troubleshooting) help, you are welcome to join our community forum or Discord. [7] I'm mostly active on the forum myself. [8] [0] https://about.gitlab.com/handbook/engineering/quality/issue-... [1] https://about.gitlab.com/direction/#how-we-plan-releases [2] https://about.gitlab.com/handbook/product/product-processes/... [3] https://gitlab.com/groups/gitlab-org/-/roadmap?state=opened&... [4] https://gitlab.com/gitlab-org/gitlab/-/issues/?label_name%5B... [5] https://about.gitlab.com/handbook/product/categories/feature... [6] https://about.gitlab.com/support/ [7] https://about.gitlab.com/community/ [8] https://forum.gitlab.com/u/dnsmichi/summary |