News for hackers. Stuff that matters.
Re:GitLab Master Plan by StavrosK on Tuesday September 13, 2016 @09:10AM (#12487830)
As a customer, I love the integrated CI and how easily I can now run tests for each commit and show pass/fail and coverage information right on the commit. We used to use Stash and Jenkins, but it was pretty hard to get the integration to work reliably.

Another thing I love is the gitlab-runner, which lets me spin up a machine and have another server to run tests on.

What I really don't love is how limited issues feel compared to JIRA. Namely, the following workflow is so hard it might as well be impossible:

* Issue gets opened by a user/assigned to a developer. * Developer has a view that's only issues that they haven't worked on or that they're working on. * After the issue has been worked on, the developer can assign it back to QA. * QA retests and closes.

This was very well served with JIRA's open -> in progress -> resolved -> closed pipeline, as well as with the views that could filter things like "show me issues assigned to me or nobody, that are not resolved or closed, ordered by priority".

We tried to do something similar with labels and the board, but it's really inconvenient, because we can't filter for "show me issues that are NOT <something>". We used a "new" label instead, but the board doesn't know that "new" is the backlog and that that label should be removed when the issue moves out of the former.

In general, we've been having problems with issues, although the milestone view is pretty fantastic.

Re:GitLab Master Plan by jobvandervoort on Tuesday September 13, 2016 @09:26AM (#12487964)
Thanks for the awesome comment and details.

> show me issues assigned to me or nobody, that are not resolved or closed, ordered by priority

Right now, GitLab orders by priority out of the box on the board. You can filter for yourself or assigned to nobody. Not both, but we're working on improving the filters (including the option to do "NOT X OR Y". [0]

> We used a "new" label instead, but the board doesn't know that "new" is the backlog and that that label should be removed when the issue moves out of the former.

Just create a list with the 'new' label and you should be good, right?

We're thinking about having different types of lists in Boards, such as 'Milestone boards' and 'Status boards'. Something like that could solve some of your requests as well.

[0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/21993

Re:GitLab Master Plan by StavrosK on Tuesday September 13, 2016 @11:44AM (#12489290)
> Just create a list with the 'new' label and you should be good, right?

Yes, but then you have a "backlog" and a "new" list, which are no different, and yet distinct :/

> Not both, but we're working on improving the filters (including the option to do "NOT X OR Y". [0]

That's fantastic, logical operators would be a great feature.

> We're thinking about having different types of lists in Boards, such as 'Milestone boards' and 'Status boards'. Something like that could solve some of your requests as well.

I think that, if you have powerful filtering functionality, then everything could just be a filter. E.g. a board would be a list of filters with two actions or an associated label (i.e. "show me all issues that are X AND Y (OR NOT Z)", and assign label B when an issue is added here and unassign it when removed). Issue lists could similarly just be a filter view ("show me the issues with assignee=me or assignee=none and status=new or not status=closed"), etc.