GitLab
GitLab Project Management Review and Pricing: Boards and Iterations
GitLab brings issue planning alongside repositories and CI/CD. Its boards turn issues into cards and can combine work from several projects at group level, giving a software team a way to discuss delivery in the same platform as implementation.
That connection matters most when GitLab is already your development home, or when consolidating the wider platform is part of the decision. A board alone is a weak reason to migrate a working code and build environment. Inspect the planning tier and deployment model together.
Boards, iterations and code references
Moving a card between board lists can change its label, assignee or milestone. Group boards combine projects; iteration-based planning organizes timeboxed work. Iterations differ from milestones, so design the group hierarchy and sprint structure around how teams actually deliver.
Free includes ordinary boards and one group issue board. Configurable scopes and iteration or status list types require Premium or Ultimate. The documented sprint setup uses roles, group structure and an iteration-filtered board, making those configuration choices part of the purchase evaluation.
Work-item references also distinguish a mention from a closing instruction in a merge request. Closing patterns can complete work automatically when the merge request merges. The current sidebar widget is generally available in GitLab 19.0, so check an older Self-Managed release before expecting the same interface. A merge records a code event; it does not establish that the change has reached users.
GitLab pricing: hosted plans and Self-Managed costs
GitLab pricing lists GitLab.com Free at five users per top-level group, 400 compute minutes per month and 10 GiB storage. Premium adds enhanced team planning and support, including paid iteration planning. Check the pricing page for the up-to-date per-user amount, currency and annual billing total for your deployment. Ultimate is quoted and adds strategic portfolio and compliance capabilities.
Self-Managed Free means supplying and operating your own storage and runners. Hosted allowances do not carry over to it. Dedicated is a separate managed, isolated deployment. Add compute, storage and any AI credits or add-ons to the seat estimate, and verify contractor roles: the Ultimate guest offer is not a universal free-contractor license.
If switching from Jira, rehearse the import
The built-in Jira importer transfers titles, descriptions and labels and supports user mapping; other unmapped metadata can become description text. Formatting may break, and complete comment or assignee preservation should not be presumed. It requires Jira read access, a configured Jira integration and GitLab Maintainer or Owner permissions.
Before moving a team, compare representative imported records against their originals. CSV, scripts and Professional Services are other paths, but their availability does not prove lossless transfer. Confirm support scope and operational ownership for the selected deployment.
Fit and alternatives
GitHub Projects is the native planning comparison if your code remains on GitHub. Jira separates a configurable tracker from the development platform. The software-team comparison can help decide whether that separation is useful.
For GitLab, evaluate one group board, a sprint configuration and a referenced merge request on the intended tier and version. That exposes the daily benefit and the administrative boundaries before a platform commitment.