Greetings Gitlab Community, Awhile back I was searching for a good scrum / kanban style interface for Gitlab.
If you've done the same you probably encountered some of these threads... https://github.com/rauhryan/huboard/issues/190 [148 votes] http://feedback.gitlab.com/forums/176466-general/suggestions/3890905-use-huboard-as-project-management-tool [422 votes] http://feedback.gitlab.com/forums/176466-general/suggestions/3840944-kanban-planning-view-for-issues [169 votes] There seems to be a demand? I do appreciate Gitlab Team tried to implement something with the "Milestone View", but to me this didn't really satisfy what I was after. So long story short, I made something myself. Here's what it looks like: <https://camo.githubusercontent.com/0b7781d4ba465c5989876a8cdc3496dfc092ecf2/687474703a2f2f6f6936302e74696e797069632e636f6d2f7272687779672e6a7067> ScrumGUI for GitLab (Github Repo) <https://github.com/Jayinthebay/scrumgui> The workflow is pretty slick I think. It basically goes something like this for a typical issue/task: - Add an issue -- store it in "Userstory/Backlog" column until you're ready to task it to someone - Assign task to project team member, move it to "Todo" (Within columns, tasks can be reordered for "prioritization") - Team member picks up the task and moves it to "In Progress" column - Team member then checks out branch for issue (e.g. git checkout -b jg_issue#2) - Team member then perform the work/code to meet criteria of the issue & pushes this feature/issue branch back to origin - Team member drags issue from "In Progress" to "For Review" -- is prompted for which commit to link to the review (e.g. jg_issue#2) - AWESOME PART: The linked issue branch/commit is automatically submitted as a merge request to DEV branch. - If approved (via ScrumGUI) then the merge to DEV is approved - You can then merge DEV to MASTER manually at your leisure for release updates In the GitLab feed, it looks something like this for a single issue/feature approval with merge: <http://s1.postimg.org/6dq4yvhzj/gitlabside.png> A lot of other little features here and there (e.g. integration with GitLab issue comments and distinguishing between user comments and git/gitlab process related noise, mapping of Gitlab roles for scrum roles, etc.) It's at the point now where we are using it internally for our own projects and it works well. I'd would like to a burndown chart in it in the future and align it more closely to scrum/agile methodology. Anyway, I have a little expense in this, and I was going back and forth on HOW I should release it. While a nice true Scrum/Kanban style board for GITLAB does seem to be unique, the concept is not. Many companies are already in the space in general (e.g. Jira, Huboard, ScrumDo). So I think I've decided to open source it and accept donations if anyone finds it useful... I'd like to recoup some expenses. If I can make some dinner/coffee money on top of that, that would be super. I'm sure you'll buy me a pizza or something right? :) I'm not quite ready to push the code to GITHUB. I don't have any experience releasing source or dealing with software licenses, so if someone experienced in these areas who might benefit from me releasing this would be kind enough to offer some tips/suggestions for type of license I should use, that would be appreciated (and it will likely expedite release/availability of this thing). Take care, Jayinthebay (JG) -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/1bc96555-bb2c-4908-8ff6-19e35c46fe4f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
