Jira vs GitLab
On this page
Jira Software is an issue tracker and agile project management application. Portfolio for Jira Portfolio is a separate add-on that enables portoflio 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 managment capabilities without the software and agile-specific functionality of Jira Software.
Jira is available via 3 deploment models:
- Cloud: SaaS version of Jira hosted and managed by Atlassian
- Server: self-managed version that can be deployed on a single server
- Data Center: self-managed version that can be deployed to multiple servers for high availability.
- From customer comment on why they won't switch from Jira:
Probably some of these features could be worked around in GitLab (e.g. by using labels exclusively). In particular for our organization we have been using Jira for much longer than GitLab. Migrating to another issue tracking system for existing project would be less than trivial, i.e. if one wants to maintain the history.
- From HackerNews JIRA customer about JRA and how it makes their developers feel:
Agreed that the problem isn't directly Jira, but (anecdotally maybe) there seems a clear correlation between Jira and unhappy developers who feel their tracker has way too much process. Jira doesn't cause the root problem, but Atlassian are profiting from it existing, and so maybe people are encouraged to use it in those ways. I'm not letting it off the hook so easily.
JIRA makes it dangerously easy to implement overly bureaucratic processes. A certain kind of organization is drawn to it for that reason. Even a healthy organization switching to JIRA can get carried away with the tools now at its disposal.
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 managment, CI/CD, and monitoring.
- Flat $10 per month for up to 10 users
- $7 per user/month for 11-100 users
- Server: $3,600 one-time payment (50 users)
- Data Center: $12,000 per year (500 users)
- Flat $10 per month for up to 10 users
- $3.50 per user/month for 11-100 users
- Server: $9,900 one-time payment (500 users)
- Data Center: n/a
- Flat $10 per month for up to 3 agents
- $20 per agent/month
- Sever: $13,200 one-time payment (50 agents)
- Data Ceneter: $60,000 per year (500 agents)
- Flat $10 per month for up to 10 users
- $5 per user/month for 11-100 users
- Small teams: $10 One-time payment for up to 10 users
- Growing teams: $13,200 one-time payment (500 users)
A few missing features in GitLab that JIRA has from this comment
- The concept of "Components" with a configurable set of default assignee's and associate component watchers (this is separate from "Labels", which also exist in Jira)
- Multiple issue types
- Configurable set of fields and screens for each issue type
- Workflow definition (e.g. allowed transitions for each issue status) for each issue type
- Fine-grained notifications control for each issue action
Plan and track work at the project and portfolio level. Manage capacity and resources together with Portfolio Management.
Plan and track work at the feature level by collecting multiple issues together in the same group.
Visualize multiple epics across time in a roadmap view
Create and manage milestones across projects, to work towards a target date from the group level. View all the issues for the milestone you’re currently working on across multiple projects.
Group Issue Board
Issue board scoped at the group level, so that you can view issues in all projects of that group.
Powerful Issue Tracker
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.
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.
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.
GitLab lets you manage issues using Agile practices by setting the weight of an issue.
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 to 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.
Explicitly mark issues as related and track their status.
Multiple assignees for issues
Assign more than one person to an issue at a time.
Time Tracking in GitLab lets your team add estimates and record time spent on issues and merge requests.
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.
Due dates for individual issues
In GitLab, you can set a due date for individual issues. This is very convenient if you have small tasks with a specific deadline.
Move issues between projects
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.
Issue board templates
Issue boards/dashboards reflect an organizations flow for processing work items. These boards can reflect individualized workflow or follow established patterns. Templates for established patterns (such as Scrum and Kanban) can make setup of new boards easier.
Issue Board Swimlanes
View horizontal swimlanes of issues in the issue board, separated by milestones or labels.
Create new issues from the Issue Board
With GitLab Issue Boards, you can create issues directly from the board and assign multiple labels allowing them to appear on multiple boards.
Construct Issue Boards around issue labels
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.
Add multiple issues to the board
From an Issue Board, you can add multiple issues to lists in the board by selecting one or more existing issues.
Configurable Issue Boards
Associate a board with a milestone, labels, an assignee, and a weight
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.
Create issue from email
Create an issue from email by sending in the issue title and description.
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.
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.
Issue Boards based on application specific query language
Define what issues show in an issue board using an application specific query language
Create, search and view issues from chat
Quickly create, view and search for issues straight from chat.
Mattermost can be automatically installed and integrated using GitLab Omnibus
Multiple Group Issue Boards
Multiple Group Issue Boards, similar to Multiple Project Issue Boards
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.
Labels provide an easy way to categorize issues or merge requests based on descriptive titles as ‘bug’, or ‘documentation’.
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.
Configurable issue closing pattern
Define your own specific keywords to close one or more issues as soon as a merge request is merged.
Enriched Markdown support
GitLab uses ‘GitLab Flavored Markdown’ (GFM). It extends the standard Markdown in a few significant ways to add some useful functionality.
Issues and merge requests templates
By adding a description template to your MRs, users who create a new issue or merge request can select a template to help them to communicate effectively.
If you feel there are inaccurate statements in this comparison, please edit this page or propose edits by creating an issue. When creating an issue, please use the "Comparison page" template and assign to @dangordon to ensure we see your suggested changes. You can also send an email to email@example.com with your suggested edits if you're unable to create an issue or edit this page.
We strive for technical accuracy and will review and update this post for inaccuracies as quickly as possible.