GitLab issues vs Axosoft

GitLab's UI is clean and intuitive. Each view is designed to not fill the screen with useless information.

It displays the activity in a feed-type way in the most prominent part of the view. On top of that, there's a toolbar with buttons which can filter this feed by pushes, merge events or comments.

On the left, there's a menu that displays all the links that take you to the different views. For example, a file directory which displays all the files in that repo, a commit view which displays all the commits in cronological order, a network and a graph view that display important information graphically etc...

All these details make GitLab's UI extremely intuitive and easy to use, no view is overflown with information and every view displays only the most useful and crucial information needed at that time.

Gitlab is a free open source project licensed under MIT. Source code for Enterprise Edition can be found here and Community Edition here.

GitLab CI makes it easy to set up CI and deployment for projects in GitLab. It supports parallel testing, multiple platforms, Docker containers and streaming build logs.

GitLab is being constantly worked on and has a new release every month on the 22nd. Updating is also very easy through a single upgrade script.

On GitLab EE (free for open-source projects only) you can set the weight of an issue during its creation (from 1 to 9) to get a better idea of how much time, value or complexity a given issue has.

Turn emails into support incident tickets. A brandable self-service portal can be created for customers to create and edit tickets without using paid Axosoft accounts.

Tasks are divided into categories and each category can have one or more workflows which are followed by tasks belonging to that category until their completion.

In other words, workflows are used to set each step tasks need to take in order to be completed. Axosoft lets users have extremely fine-grained control over workflows and by extension, the whole lifecycle of each task. Each step in a workflow can be named and you can choose which fields are updated when a step is complete. This way you can automatically tweak tasks as they progress (you can set tasks to belong to different users once a step is complete, you can even change workflows for a task if a certain step is taken).

Each item has a PDF button (among others) which lets you export all the information related to that particular item in PDF format.

Axosoft lets users pretty much create custom dashboards any time they want to view only a specific part of the project data and information.

You can choose which tabs to keep open and even how tasks are shown and what kind of data is shown for each task. This way you can see for example how much time is left in a sprint, or how much capacity the team has left to finish the project.