I'm seriously impressed with Gitlab's issue system. I mean, it's apparent that they are great at git hosting and repository collaboration but the issue management system is really good. Epics, backlogs, stories, labels, tags, milestones, boards, roadmaps, it's all there.
I was just having a conversation with a coworker about Jira vs Gitlab and why it doesn't make sense for us to switch to Jira over using Gitlab issues. After test driving it for a few weeks and now with a little "nudge" of backing from Arch with this post about how they have migrated to it, I was able to convince my coworker that Gitlab issues is more than enough for what we do and that adding Atlassian on top of that would only add to costs. FWIW, I love Atlassian Jira+Confluence duo. I don't like Bitbucket at all. It feels very antiquated and Jenkins-like. The UI theme isn't the issue, it's the layout, the nav, the construction that just rubs me the "we don't care about your productivity" way.
I was just having a conversation with a coworker about Jira vs Gitlab and why it doesn't make sense for us to switch to Jira over using Gitlab issues. After test driving it for a few weeks and now with a little "nudge" of backing from Arch with this post about how they have migrated to it, I was able to convince my coworker that Gitlab issues is more than enough for what we do and that adding Atlassian on top of that would only add to costs. FWIW, I love Atlassian Jira+Confluence duo. I don't like Bitbucket at all. It feels very antiquated and Jenkins-like. The UI theme isn't the issue, it's the layout, the nav, the construction that just rubs me the "we don't care about your productivity" way.