Jira vs GitLab

GitLab compared to other DevOps tools

On this page

Summary

Jira Software is an issue tracker and agile project management application. Portfolio for Jira Portfolio is a separate add-on that enables portfolio management in Jira Software. Jira Service Desk is a separate application to enable IT and customer service capablilities. Jira Core is a scaled down version of Jira Software that contains the general project management capabilities without the software and agile-specific functionality of Jira Software.

Jira is available via 3 deploment models:

Weaknesses

Comments/Anecdotes

Resources

Integrations

GitLab has Jira integration that allows Jira Software to be used as an issue tracker for the planning stage while using GitLab for the rest of the DevOps lifecycle: source code management, CI/CD, and monitoring.

Pricing

Jira Software pricing

Portfolio for Jira pricing

Jira Service Desk pricing

Jira Core pricing

Comparison

A few missing features in GitLab that JIRA has from this comment

FEATURES

Issues

Quickly set the status, assignee or milestone for multiple issues at the same time or easily filter them on any properties. See milestones and issues across projects.

Learn more about the Issue Tracker

Description Templates

By adding a description template to your issues or merge requests, users who create a new issue or merge request can select a template to help them to communicate effectively.

Learn more about GitLab Description Templates

GitLab Flavored Markdown

GitLab uses 'GitLab Flavored Markdown' (GFM). It extends the standard Markdown in a few significant ways to add some useful functionality.

Learn more about GitLab Flavored Markdown

Labels

Labels provide an easy way to categorize issues, merge requests, or epics based on descriptive titles as 'bug', or 'documentation'.

Learn more about GitLab Labels

Issue Weights

GitLab lets you manage issues using Agile practices by setting the weight of an issue.

Read our Issue Weights documentation

Milestones

Create and manage milestones at both the project and group levels, viewing all the issues for the milestone you’re currently working on, representing an Agile sprint or a release.

Learn more about Milestones

Issue Due Dates

In GitLab, you can set a due date for individual issues. This is very convenient if you have small tasks with a specific deadline.

Due dates documentation

Multiple Issue Assignees

Assign more than one person to an issue at a time.

Read our Multiple Assignees Documentation

Confidential Issues

Keep your information secure with Confidential Issues. With GitLab, you can create confidential issues visible only for project members with Reporter access level or above.

Learn more about Confidential Issues

Related Issues

Explicitly mark issues as related and track their status.

Learn more about Related Issues

Move Issue to Another Project

You can move issues between projects in GitLab. All links, history and comments will be copied and the original issue will reference the newly moved issue. This makes working with multiple issue trackers much easier.

Learn more about moving issues between projects

Mark Issue as Duplicate

Mark an issue as a duplicate of another issue, closing it.

Learn more about marking duplicate issues

New Issue via Email

Create an issue from email by sending in the issue title and description.

Create issue from email

Burndown Charts

GitLab provides Burndown Charts as part of Milestones. This allows users to better track progress during a sprint or while working on a new version of their software.

Read our Burndown Chart Documentation

Project Issue Board

GitLab has Issue Boards, each list of an Issue Board is based on a label that exists in your issue tracker. The Issue Board will therefore match the state of your issue tracker in a user-friendly way.

Learn more about GitLab Issue Boards

Group Issue Board

Issue board scoped at the group level, so that you can view issues in all projects of that group.

Learn more about Group-level Issue Boards

Multiple Project Issue Boards

Large companies often have hundreds of different projects, all with different moving parts at the same time. GitLab Enterprise Edition allows for multiple Issue Boards for a single project so you can plan, organize, and visualize a workflow for a feature or product release. Multiple Issue Boards are particularly useful for large projects with more than one team or in situations where a repository is used to host the code of multiple products.

Multiple Project Issue Boards

Multiple Group Issue Boards

Multiple Group Issue Boards, similar to Multiple Project Issue Boards

Multiple Groject Issue Boards

Issue Board Label Lists

An Issue Board is based on its project's label structure, therefore, it applies the same descriptive labels to indicate placement on the board. GitLab issues can appear on multiple issues and they still have meaning without the context of a particular board.

Learn more about labels and Issue Boards

Issue Board Configuration

Associate a board with a milestone, labels, an assignee, and a weight

Learn more about configurable Issue Boards

Issue Board Focus Mode

Get more information at a time with the Issue Board focus mode, which removes all unnecessary elements from the screen to show your Issue Boards.

Learn more about Issue Board focus mode

Add Multiple Issues to Project Issue Board

From an Issue Board, you can add multiple issues to lists in the board by selecting one or more existing issues.

Learn how to add multiple issues to your Issue Board.

New Issue in Issue Board List

With GitLab Issue Boards, you can create issues directly from the board and assign multiple labels allowing them to appear on multiple boards.

Learn how to create a new issue from the Issue Board

Issue Board Epic Swimlanes

View epics as swimlanes in an issue board.

See epic for details

Issue Board Types

Issue boards/dashboards reflect an organizations flow for processing work items. These boards can reflect individualized workflow or follow established patterns. Issue board types with established patterns (such as Scrum and Kanban) can make setup of new boards easier.

See issue for details

Issue Board Configuration with Advanced Logic

Define what issues show in an issue board using advanced Boolean logic.

See epic for details

Time Tracking

Time Tracking in GitLab lets your team add estimates and record time spent on issues and merge requests.

Learn more about Time Tracking

Multi-level Epics

Plan and track strategies, initiatives, and features with multi-level epics that collect issues together.

Learn more about Epics

Roadmaps

Visualize multiple epics across time in a roadmap view.

Learn more about Roadmaps

Out-of-the-box Agile Reporting

Teams have access to more than a dozen out-of-the-box reports with real-time, actionable insights into how their team is performing sprint over sprint. Example reports are sprint burndown, epic burndown, cumulative flow diagram, velocity chart, burn up chart, and sprint report.

Read our Burndown Chart Documentation

Service Desk

Allow external users to create issues in your GitLab instance without an account and without access to anything except their issue. Manage tickets from the GitLab interface.

Learn more about Service Desk

Portfolio Management

Plan and track work at the project and portfolio level. Manage capacity and resources together with Portfolio Management.

Learn more about Portfolio Management

Create, search and view issues from chat

Quickly create, view and search for issues straight from chat.

Read the documentation on Slash commands

Mattermost integration

Mattermost can be automatically installed and integrated using GitLab Omnibus

Read the documentation on Mattermost integration

Multiple integrations

GitLab can integrate with Authentication and Authorization (LDAP / AD) mechanisms, multiple 3rd party services, CI/CD, and other tools such as ALM, PLM, Agile and Automation tools.

Learn more about GitLab's integrations

Automatically close issue(s) when a merge request is merged

With GitLab, you can use specific keywords to close one or more issues as soon as a merge request is merged.

Learn more about automatically closing issues

Configurable issue closing pattern

Define your own specific keywords to close one or more issues as soon as a merge request is merged.

Learn more about automatically closing issues