GitLab compared to other DevOps tools

Redmine vs GitLab

On this page

Summary

Redmine is a free and open source, web-based project management and issue tracking tool. It allows users to manage multiple projects and associated sub-projects. It features per project wikis and forums, time tracking, and flexible, role-based access control. It includes a calendar and Gantt charts to aid visual representation of projects and their deadlines. Redmine integrates with various version control systems and includes a repository browser and diff viewer.

Redmine is written using the Ruby on Rails framework. It is cross-platform and cross-database and supports 34 languages.

Comments/Anecdotes

  • From a user on Quora

    it's flexible, highly customizable, (you can choose between various templates, plugins, etc.) It's open source and free to use. [and] the user interface doesn't overwhelm you.

    Since it's highly customizable you really have to dig yourself into it at first in order to create a great experience for your team members and colleagues / clients

Resources

Pricing

  • $0 - Redmine is free and open source
  • However, TCO can be high, as Redmine is similar to Jenkins, with lots of desired functionality available through plugins (944 as of 2018-10-17), some of which are maintained, and some of which are not.
  • There are also companies which sell plug-in sets, for example to add Agile functionality (eg. RedmineUP Agile Plugin). Prices vary.

Comparison

FEATURES

Kanban

Able to support the flow based approach of Agile - Kanban software delivery. Specific features would include: Issues, Kanban boards, burn up, cumulative flow diagram.

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

Issue Weights

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

Read our Issue Weights documentation

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.

Multiple Project Issue Boards

Related issues

Explicitly mark issues as related and track their status.

Learn more about Related Issues

Multiple assignees for issues

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

Read our Multiple Assignees Documentation

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

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.

Due dates documentation

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.

Learn more about moving issues between projects

Create new branches from issues

In GitLab, you can quickly create a new branch from an issue on the issue tracker. It will include the issue number and title automatically, making it easy to track which branch belongs to which issue.

See how in our documentation

Quick actions

GitLab provides a convenient way to change metadata of an issue or merge request without leaving the comment field with slash commands.

Documentation about quick actions

Issue Board Assignee Lists

Issue board lists that pull in issues assigned to a given user

Documentation about Issue Board Assignee Lists

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.

Learn more about GitLab Issue Boards

Issue Board Swimlanes

View horizontal swimlanes of issues in the issue board, separated by milestones or labels.

Issue Board Swimlanes

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.

Learn how to create a new issue from the Issue Board

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.

Learn more about labels and Issue Boards

Configurable Issue Boards

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

Create issue from email

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

Create issue from email

Lock Discussion

Lock down continued discussion in an issue or merge request as a Master role or higher, to prevent further abuse, spam, or unproductive collaboration.

Lock Discussion

Drag and drop tasks

You can change the order of tasks in markdown on GitHub. GitLab does not have this ability, but is considering implementing it.

See the GitLab issue to implement this

SUPPORT file link

Link from new issues to a SUPPORT file, pointing to support resources.

See the GitLab issue to implement this

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

Issue Boards based on application specific query language

Define what issues show in an issue board using an application specific query language

Learn more about Configuring GitLab Issue Boards

Export issues as CSV

Issues can be exported as CSV from GitLab and are sent to your default notification email as an attachment.

Learn more about exporting issues as CSV

Custom Notifications

Be notified by email, Slack, or ToDos anytime there are changes to an issue or merge request.

Learn more about Custom Notifications

Create, search and view issues from chat

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

Read the documentation on Slash commands

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

Enriched Markdown support

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

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.

Learn more about GitLab Description Templates

Built-in and custom project templates

When creating a new project, you can choose to kickstart your project from a predefined template that already has some working example code and CI preconfigured. In addition, you can define a custom project templates by assigning a group. Child projects of this group are available as templates when creating a new project.

Read more about Project templates

User status message

Define and show your personal status message via an Emoji and text message, exposed on your profile page and on any comment and author line.

Learn more about Status messages

Download as PDF

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 dgordon@gitlab.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.

GitLab is the trademark of GitLab, Inc. All other logos and trademarks are the logos and trademarks of their respective owners.

Try GitLab Ultimate risk-free for 30 days.

No credit card required. Have questions? Contact us.

Try GitLab Ultimate risk-free for 30 days.

No credit card required. Have questions? Contact us.