Re:GitLab Master Plan
by jamie_ca on Tuesday September 13, 2016 @11:19AM
(#12489018)
At work, the worst thing we've done this year from a product management standpoint is migrate from Github Issues to JIRA.
It was done for the right reason: to have a single place for all our work (JIRA for feature planning/sprint planning/dev+qa tracking, Confluence for documentation) but it's been hobbled because we still need github to coordinate code review + merges.
The better solution would have been to stay with Github and use Huboard or something to layer on the swimlane sprint planny stuff, but keep _all_ our info in GH Issues.
Moving entirely to Gitlab in a year or so once things have matured would be a great win for us, I'm sure.
It was done for the right reason: to have a single place for all our work (JIRA for feature planning/sprint planning/dev+qa tracking, Confluence for documentation) but it's been hobbled because we still need github to coordinate code review + merges.
The better solution would have been to stay with Github and use Huboard or something to layer on the swimlane sprint planny stuff, but keep _all_ our info in GH Issues.
Moving entirely to Gitlab in a year or so once things have matured would be a great win for us, I'm sure.