6 ms·
I gotta say--I love gitlab. We use a self-hosted version of it and it's fantastic. I think the best thing about it is the extra features don't bog down the in
by sov 9y ago
I gotta say--I love gitlab. We use a self-hosted version of it and it's fantastic. I think the best thing about it is the extra features don't bog down the interfaces. With tools like JIRA, or even github, it seems that to "use more" of it, you kinda nuke the new user experience by making interactions unnecessarily complicated. GitLab seems to generally work and keep simple while adding a whole lot--they balance it well.
Recently, I added a webhook that takes all our GitLab pushes and parses out JIRA information and automatically handles that sort of business-level logic (issue handling, visibility, etc.), which means I spend less time boring myself to death in JIRA. It's just one facet of what I appreciate about GitLab.
- unspecified 9y ago> Recently, I added a webhook that takes all our GitLab pushes and parses out JIRA information and automatically handles that sort of business-level logic Have you found a good solution for auto-linking to JIRA tickets from GitLab comments/commits/etc without turning on the the included JIRA Integration? I want to continue using Gitlab's native issues, and the included JIRA integration replaces the native Gitlab issues with JIRA tickets, which is such a colossally boneheaded idea.
- victorwu 9y agoThank you for the feedback. As of GitLab 9.4, you are able to use both JIRA integration together with native GitLab issues. If JIRA integration is configured inside your GitLab project, the issues menu item in the navigation still goes to native GitLab issues, and you can use GitLab issues as usual.