For those of us that have had modules migrated to GitLab:

The old system may be gone but the new one has new organizational tools!

Using this module as an example git.drupalcode.org/project/commerce_giftcard/-/work_items

The GitLab admins migrated the metadata from your existing issues into labels. It can feel really cluttered and confusing with the defaults. You can change that!

Each project can manage it's own labels, including the colors of them.

In the example module I linked I went and changed all of the unimportant tags to the color EEEEEE_1. So priority::normal and priority::minor are now no longer alert red. The issues marked as major and critical stand out now. The version labels, the type (code, user interface) are all desaturated now. You can still sort and filter by them but they don't compete for attention from the critical labels we're used to seeing in the old system: State and Type

In addition to the labels, you can create milestones. In this project I created milestones for the three major parts of the module that needs work to get to a stable release: Admin experience, customer experience, and code quality. The relevant issues were marked with these milestones and now stand apart from the other features and ideas that haven't been evaluated yet or are nice to haves. You can use milestones for anything. If you have a goal with the module, use them to organize issues relevant to it. The milestone page is different than using labels. You get a board showing what's been done, what is in progress, what needs to be done still. Example: git.drupalcode.org/project/…/2#…