Transparency is good and it can also mean that there is a lot of information to understand, especially when trying to determine when an Issue on the roadmap may ship. This page highlights the pieces of information that can help give guidance on what state an issue is in and when it might ship. This is especially helpful for giving answers to customers and stakeholders when setting the correct expectations.
GitLab's Product Development Workflow describes all the different steps that take an issue from ideation to validation to design to development and finally to getting in the hand of end-users. It has full details about every step of the workflow and can be read for specific details.
There are a few pieces of info to understand when an issue might ship. Looking at each of these in combination with the others should help you understand if an item will ship in the current or a future iteration.
workflow::<current state>label shows what state the Issue is currently at in the Product Development Workflow. The various states of the label mean different things.
In general, if an issue is in
workflow::verification it is very close to shipping. Other states mean
that the issue will likely change DRI
several times and may or may not ship in the marked milestone.
Stretchlabels give an indiciation of engineering's confidence that an issue will complete in the assigned milestone or not, with the former being a high-level of confidence and the latter being a lower possibility. If the issue has neither of these labels and is assigned to the current milestone, it is unlikely to ship.
Issues are frequently included as part of a larger Epic of work. Epics may have multiple issues, each with a seperate scope and assigned milestones. It can be helpful to look at the Epic an issue is contained in to understand what other related work is planned to understand when everything will be shipped and usable by users.
If you are still not sure what state an issue is in and want to ensure you set the correct expectations with the customer, please @mention the responsible Product Manager, on the issue or epic, so they can clarify.