On Wed, 2017-12-06 at 18:49 +0100, Carlos Soriano wrote: > I have good news, after few meetings and discussions with GitLab we > reached an agreement on a way to bring the features we need and to > fix our most important blockers in a reasonable time and in a way > that are synced with us.
Hi, couple other things I faced when I touched gitlab. How is the test instance different from the one GNOME is maybe going to use? Though I do not see basic things even in gitlab.com interface, thus maybe doesn't matter. Let's start with easy things: a) See the second comment of https://gitlab-test.gnome.org/mcrha/test/issues/2 It shows like three lines of text (one line, then empty line, then third line). When you edit that comment you'll see I made it several lines, not only three - the interface is ignoring my Enter-s. Am I supposed to use some crazy tag when I want to divide paragraphs and/or write simple lines? b) How do I reply to a comment? I really do not see it (call it usability issue, because this is quite unintuitive comparing to bugzilla, where I see beside each comment a [reply] link which does fancy things and saves me time). Oh, I've received an answer from the upstream, there's a keyboard shortcut for it, which involves selection on the page. I really cannot get such things when opening the interface (not the manual). c) my current work flow with bugzilla involves having opened *one* tab in the browser with a search which contains a list of bugs changed since some date for four different products. I refresh it in the morning to see newly added bugs and eventually react to them (I know, that's a silly idea to take care of newly added bugs where reporters are active the most). How do I do the same in gitlab, while: 1) the space will not be wasted, because I dislike scrolling when it's unnecessary (and here it is); 2) it will not be four different tabs in the browser? d) I cannot set labels on my test project for some reason. They are probably good for searching, I don't know, but trying "/label ~xxx" in the comment just doesn't do anything (is that the right and only way to set label on an issue by commenting with a code-like tags?). I opened an issue in gitlab.com (see my previous mail in this thread), maybe I do not have permission for it, in my own project? The test instance also doesn't auto-complete any label, which may or may not be related (per-project labels disabled/impossible?). I know you can easily RTFM me, but do you know what? I didn't read any single word of the bugzilla manual and I've been able to work with it with no problem. Weird, I know. While there is expected some difference, I think I should not be hunting for basic usage hints. Bye, Milan _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list