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=n...

And no, tags are not enough.

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

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

> 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)

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!