5 ms·

I love how responsive our local (departmental) instance of GitLab CE is -- it's downright snappy compared to the corporate instance of JIRA. We love the issue

I love how responsive our local (departmental) instance of GitLab CE is -- it's downright snappy compared to the corporate instance of JIRA. We love the issue tracking subsystem of GitLab and use it as our main ticketing system. We've done a few talks on Git basics to help increase adoption, and are doing a free webinar "Git Foundations: Basic Concepts and Definitions" next week: https://www.eventbrite.com/e/git-foundations-basic-concepts-and-definitions-tickets-26937970194 https://www.eventbrite.com/e/git-foundations-basic-concepts-... This is the sort of result it makes us very happy to achieve: "I have got by on minimum understanding of Git for a couple of years now--this really brought up my confidence in using Git. After I learned the Git internals, the esoteric commands really started falling into place." --Nicholas Santucci, Monitoring and Performance Engineer

jobvandervoort 10y ago
That's some great feedback, thanks! Any feature requests for Issues? If you plan on doing physical events, drop me an email (job at gitlab).
- atsaloli 10y ago
  We've done three physical events already. :-) I'll email you! Our next physical event will be teaching at Ohio Linux Fest (https://ohiolinux.org/olfi/ https://ohiolinux.org/olfi/)
- cdawzrd 10y ago
  Feature requests for Issues: priorities, and states other than open and closed. These are the biggest things keeping us from using GitLab issues rather than an external tool. We need to be able to set priorities (ideally customizable, but at minimum high/med/low). We can kind of do that through labels, but it's messy because you can only search for one label at a time (no boolean combinations of labels). Right now, when you assign an issue to a user, it's considered "in progress", and from there it can either be unassigned or closed. It would be nice to separate the state of the issue from the assigned user, since in our current workflow we assign many issues to a user, but that user might only be working on a few of them at a time. Using our current bug tracker, we can differentiate between "Open, unassigned", "Open, assigned", "Open, in progress", "Fixed", "Verified", "Closed", etc. I know having a completely customizable state diagram for issues is a big software task, but maybe there is some intermediary level of complexity that would allow better tracking of what is actually being worked on now vs. what is assigned to people.
  - haynes 10y ago
    Actually you can add priorities to labels :) http://docs.gitlab.com/ce/user/project/labels.html#prioritize-labels http://docs.gitlab.com/ce/user/project/labels.html#prioritiz... You can also search for several labels in the current release. Just select some in the dropdown :)
atsaloli 10y ago
Wow. The power of HN. We did our webinar today and had attendees from the Netherlands, Germany, Serbia and the US. It was exciting to have an international audience.

jobvandervoort 10y ago

That's some great feedback, thanks! Any feature requests for Issues? If you plan on doing physical events, drop me an email (job at gitlab).

atsaloli 10y ago
We've done three physical events already. :-) I'll email you! Our next physical event will be teaching at Ohio Linux Fest (https://ohiolinux.org/olfi/ https://ohiolinux.org/olfi/)
cdawzrd 10y ago
Feature requests for Issues: priorities, and states other than open and closed. These are the biggest things keeping us from using GitLab issues rather than an external tool. We need to be able to set priorities (ideally customizable, but at minimum high/med/low). We can kind of do that through labels, but it's messy because you can only search for one label at a time (no boolean combinations of labels). Right now, when you assign an issue to a user, it's considered "in progress", and from there it can either be unassigned or closed. It would be nice to separate the state of the issue from the assigned user, since in our current workflow we assign many issues to a user, but that user might only be working on a few of them at a time. Using our current bug tracker, we can differentiate between "Open, unassigned", "Open, assigned", "Open, in progress", "Fixed", "Verified", "Closed", etc. I know having a completely customizable state diagram for issues is a big software task, but maybe there is some intermediary level of complexity that would allow better tracking of what is actually being worked on now vs. what is assigned to people.
- haynes 10y ago
  Actually you can add priorities to labels :) http://docs.gitlab.com/ce/user/project/labels.html#prioritize-labels http://docs.gitlab.com/ce/user/project/labels.html#prioritiz... You can also search for several labels in the current release. Just select some in the dropdown :)

atsaloli 10y ago

Wow. The power of HN. We did our webinar today and had attendees from the Netherlands, Germany, Serbia and the US. It was exciting to have an international audience.