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)
> if you have some already grown setup (it's not exactly easy to solve so no blame to Gitlab here)
Thanks :-) We do intend to offer a good solution here, so these are valuable points.
> - 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
We added a very basic issues import from a CSV file recently (https://docs.gitlab.com/ee/user/project/issues/csv_import.ht...), as a sort of basic MVC of this.
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.
That's correct. We have https://gitlab.com/gitlab-org/gitlab-ce/issues/27204 open for this if you'd like to contribute there, or even just add a thumbs-up emoji.
> - 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.
Also correct! We have https://gitlab.com/gitlab-org/gitlab-ce/issues/54118 and https://gitlab.com/gitlab-org/gitlab-ee/issues/3803 open for this, but I'm not sure if either exactly meets your needs. Feel free to open a new issue and ping me (@smcgivern on GitLab) if they don't.
> - 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)
For workflows you can see https://gitlab.com/gitlab-org/gitlab-ee/issues/2059 and specifically https://gitlab.com/gitlab-org/gitlab-ee/issues/2059#note_148.... We do intend to cover this area, we're just quite there yet.