Ohh, I really have to stop making snarky comments here :)
So I actually looked at migrating to Gitlab due our JIRA pains but it's not really possible if you have some already grown setup (it's not exactly easy to solve so no blame to Gitlab here)
- The work-log issue is not solved as far as I understood the documentation, it's possible to have external users to hide internal projects but once you are on a project time-tracking information is visible.
- From a quick glance over the docs it looks like reporting on tracked time is also not possible out of the box - and probably not across projects - we use Tempo Timesheets on JIRA for that, the slash commands /spend /estimate are probably okay for devs but we also have other users that can deal with the fields in JIRA.
- It looks like the whole custom fields on issues is still in the works (we use that quite heavily) and there is no concept of workflows (we also have some custom setup there)
- Servicedesk looks neat through.
Don't get me wrong - this reads like: I want all JIRA features in Gitlab - maybe that's a stupid idea, for a new project I'd probably just use Gitlab and see how are I come.
Sean already did a great job responding to each point here. Just want to add one more quick one. We are working on key-value labels right now, and we think it will solve many of the problems of custom fields. Feel free to take a look and add some comments. Thanks!
I've asked the product manager in the issue you linked if we're considering this in the medium term.
> - The work-log issue is not solved as far as I understood the documentation, it's possible to have external users to hide internal projects but once you are on a project time-tracking information is visible.
> - From a quick glance over the docs it looks like reporting on tracked time is also not possible out of the box - and probably not across projects - we use Tempo Timesheets on JIRA for that, the slash commands /spend /estimate are probably okay for devs but we also have other users that can deal with the fields in JIRA.
> - It looks like the whole custom fields on issues is still in the works (we use that quite heavily) and there is no concept of workflows (we also have some custom setup there)
So I actually looked at migrating to Gitlab due our JIRA pains but it's not really possible if you have some already grown setup (it's not exactly easy to solve so no blame to Gitlab here)
- no JIRA import (it's possible with some REST-API fighting), but something easy would be nice: https://gitlab.com/gitlab-org/gitlab-ee/issues/2780
- The work-log issue is not solved as far as I understood the documentation, it's possible to have external users to hide internal projects but once you are on a project time-tracking information is visible.
- From a quick glance over the docs it looks like reporting on tracked time is also not possible out of the box - and probably not across projects - we use Tempo Timesheets on JIRA for that, the slash commands /spend /estimate are probably okay for devs but we also have other users that can deal with the fields in JIRA.
- It looks like the whole custom fields on issues is still in the works (we use that quite heavily) and there is no concept of workflows (we also have some custom setup there)
- Servicedesk looks neat through.
Don't get me wrong - this reads like: I want all JIRA features in Gitlab - maybe that's a stupid idea, for a new project I'd probably just use Gitlab and see how are I come.