Manage Team

On this page


The responsibilities of this team are described by the Manage product category. Among other things, this means working on GitLab's functionality around user, group and project administration, authentication, access control, and subscriptions.

In GitLab issues, questions should start by @ mentioning the Product Manager for the Manage product category. GitLabbers can also use #g_manage.

How we work


We plan in monthly cycles in accordance with our Product Development Timeline. Release scope for an upcoming release should be finalized by the 1st.

To scope the release, Product is responsible for maintaining a prioritized list of issues. We use this prioritization board as the SSOT. Issues are tagged with the "prioritized" label and stack-ranked in the respective column. We use the following timeline:

During the release

Developers will start the release with assigned issues. If a developer has completed work on an issue, they may open the prioritization board and begin working on the next prioritized issue. Issues should be worked on in priority order (the "prioritized" column will always be sorted by descending priority; the issue at the top is most important).


After the 8th, the Manage team conducts an asynchronous retrospective. You can find current and past retrospectives for Manage in