Having switched over for a week or two now to a self-hosted instance, there are some major workflow issues we've encountered. Odds are good that some are just

Having switched over for a week or two now to a self-hosted instance, there are some major workflow issues we've encountered. Odds are good that some are just undiscoverd features/user error, but: * Navigation between 'root' project and per-user forks is terrible. There's no way I can see to go from the root proj (where all the issues/MRs are) to my fork. All the necessary data is available over the API, just not present on in the UI. * Issue labelling is kinda nasty. You default to no labels for a new project, but you can 'generate' the default set. If you want to add a new label from teh 'new issue' page, it doesn't show up as an option after adding. Make it a modal or refresh teh list or something. * You don't seem to eb able to search by commit # in the search fields? * 'merge this MR' button sometimes just arbitrarily fails, and refreshign the page and hitting it again will work (no commits/repo changes in teh meantime) * No equiv. of the github 'network graph' that also shows other forks. * It took a bunch of pissing around to disable gravatar which was giving mixed content SSL warnings even though it shouldn't. * Live preview of teh markdown input for comments/messages would be nice, especially with some apparently odd heuristics for deciding whether to autolink something like a same-repo/file:line type. * Having read the various docs I can find a few times now, I still have no clue how to set up gitlab-CI on a self-hosted instance. As I say, some of this is probably just not knowing where things are, but it's not for want of looking.