5 ms·

We use heavily gitlab-CE for VideoLAN (VLC, x264) on our hosted infra, and so far we're very happy about it. The only part blocking us from moving completely t

by jbk 10y ago

We use heavily gitlab-CE for VideoLAN (VLC, x264) on our hosted infra, and so far we're very happy about it. The only part blocking us from moving completely to gitlab and deprecate everything else is mostly the limited issues tracker (compared to trac, for example).

theunquietone 10y ago
Great to hear you're happy with GitLab CE. What features do you need in issue tracker that we don't currently have? Would love to learn more.
- jbk 10y ago
  Well, mostly, I believe we need support for custom fields, so we have for each ticket, the Platform, Component, Branch, Type, etc. And those fields can be queried or made mandatory. You can get then queries like: https://trac.videolan.org/vlc/query?status=assigned&status=new&status=reopened&component=!Bindings%3A+LibVLC+%28native+API%29&component=!Web+plugin%3A+Mozilla&summary=~asf&summary=~wmv&summary=~wma&summary=~mms&group=component&col=id&col=summary&col=component&col=status&col=type&col=priority&col=milestone&report=32&order=component https://trac.videolan.org/vlc/query?status=assigned&status=n... And no, tags are not enough.
  - jobvandervoort 10y ago
    We have a few requests for custom fields [0], but we're worried with the complexity that it adds to the application. We might start to look into this again after we've shipped better issue filtering, so that custom fields can actually be used effectively. [1] [0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/8988 https://gitlab.com/gitlab-org/gitlab-ce/issues/8988 [1]: https://gitlab.com/gitlab-org/gitlab-ce/issues/21993 https://gitlab.com/gitlab-org/gitlab-ce/issues/21993
    - jbk 10y ago
      > We have a few requests for custom fields [0], but we're worried with the complexity that it adds to the application. I'm not surprised, but for us, it's mandatory to replace trac (or bugzilla)
      - connorshea 10y ago
        If you could chime in on one of those threads with your use-case and a mention of the VLC project it may help get the ball rolling a bit faster :) Even better if you have examples of useful fields you've used!
zegerjan 10y ago
Could you explain what you mis? Or link some issues? I'd love to hear more about this.
- chaghi 10y ago
  Not OP, but I'm on the same boat. We've been using a self-hosted GitLab CE instance for more than three years now, but we can't use the bare-bones approach of GitLab for issues tracking. Trac allows us to fully customize the issues workflow, even for individual projects. We can have custom fields. We use several plugins (the extensibility of Trac is second to none!), even a few developed in-house, implementing custom validations and/or custom functionality. Trac is very lightweight (as GitLab issues), but much, much more powerful and flexible. When you need the extra functionality, you can enable it, or install some 3rd party plugin that provides it, or develop your own plugin or component (which is really easy), without turning the whole thing in a bloated mess (like Jira). The only thing I don't like about Trac is its glacial development speed, and its UI, which turns older and more outdated every year...
  - jbk 10y ago
    > We can have custom fields. Yep, that's what I need.
  - 1wd 10y ago
    Can you expand a bit about what makes the UI outdated? How should a updated UI look like?
    - chaghi 10y ago
      Sure. Please note I'm referring to Trac's UI, not GitLab's. * it sucks on mobile. It's no responsive. At all; * it's 2016 and I can't drag&drop a file to upload an attachment. Yes, there are a couple of 3rd party plugins that solve this, but this is one of those components that should have been added to the core ages ago; * visualizing the work to do is harder than it should. A "visual" panel (like the one introduced by GitLab in its latest version) with drag&drop would be awesome. * it's hard to customize. Things like changing colors, icons, padding, alignment, fonts are not at all straightforward unless you're willing to overwrite quite a lot of Trac's core CSS, and deal with the problems that might arise when you update. Trac rocks in extensibility and flexibility in almost every aspect, except for its UI and layout;

by jbk 10y ago

theunquietone 10y ago

Great to hear you're happy with GitLab CE. What features do you need in issue tracker that we don't currently have? Would love to learn more.

jbk 10y ago
Well, mostly, I believe we need support for custom fields, so we have for each ticket, the Platform, Component, Branch, Type, etc. And those fields can be queried or made mandatory. You can get then queries like: https://trac.videolan.org/vlc/query?status=assigned&status=new&status=reopened&component=!Bindings%3A+LibVLC+%28native+API%29&component=!Web+plugin%3A+Mozilla&summary=~asf&summary=~wmv&summary=~wma&summary=~mms&group=component&col=id&col=summary&col=component&col=status&col=type&col=priority&col=milestone&report=32&order=component https://trac.videolan.org/vlc/query?status=assigned&status=n... And no, tags are not enough.
- jobvandervoort 10y ago
  We have a few requests for custom fields [0], but we're worried with the complexity that it adds to the application. We might start to look into this again after we've shipped better issue filtering, so that custom fields can actually be used effectively. [1] [0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/8988 https://gitlab.com/gitlab-org/gitlab-ce/issues/8988 [1]: https://gitlab.com/gitlab-org/gitlab-ce/issues/21993 https://gitlab.com/gitlab-org/gitlab-ce/issues/21993
  - jbk 10y ago
    > We have a few requests for custom fields [0], but we're worried with the complexity that it adds to the application. I'm not surprised, but for us, it's mandatory to replace trac (or bugzilla)
    - connorshea 10y ago
      If you could chime in on one of those threads with your use-case and a mention of the VLC project it may help get the ball rolling a bit faster :) Even better if you have examples of useful fields you've used!

zegerjan 10y ago

Could you explain what you mis? Or link some issues? I'd love to hear more about this.

chaghi 10y ago
Not OP, but I'm on the same boat. We've been using a self-hosted GitLab CE instance for more than three years now, but we can't use the bare-bones approach of GitLab for issues tracking. Trac allows us to fully customize the issues workflow, even for individual projects. We can have custom fields. We use several plugins (the extensibility of Trac is second to none!), even a few developed in-house, implementing custom validations and/or custom functionality. Trac is very lightweight (as GitLab issues), but much, much more powerful and flexible. When you need the extra functionality, you can enable it, or install some 3rd party plugin that provides it, or develop your own plugin or component (which is really easy), without turning the whole thing in a bloated mess (like Jira). The only thing I don't like about Trac is its glacial development speed, and its UI, which turns older and more outdated every year...
- jbk 10y ago
  > We can have custom fields. Yep, that's what I need.
- 1wd 10y ago
  Can you expand a bit about what makes the UI outdated? How should a updated UI look like?
  - chaghi 10y ago
    Sure. Please note I'm referring to Trac's UI, not GitLab's. * it sucks on mobile. It's no responsive. At all; * it's 2016 and I can't drag&drop a file to upload an attachment. Yes, there are a couple of 3rd party plugins that solve this, but this is one of those components that should have been added to the core ages ago; * visualizing the work to do is harder than it should. A "visual" panel (like the one introduced by GitLab in its latest version) with drag&drop would be awesome. * it's hard to customize. Things like changing colors, icons, padding, alignment, fonts are not at all straightforward unless you're willing to overwrite quite a lot of Trac's core CSS, and deal with the problems that might arise when you update. Trac rocks in extensibility and flexibility in almost every aspect, except for its UI and layout;