Re: GitLab update: Moving to the next step

On 7 December 2017 at 17:01, Milan Crha <mcrha redhat com> wrote:
On Wed, 2017-12-06 at 18:49 +0100, Carlos Soriano wrote:

a) See the second comment of
   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?

The comment format is Markdown; you break paragraph by adding an empty line.

b) How do I reply to a comment?

Select the text in the comment you wish to reply to, hit 'r'; it'll
put the selection, already quoted, in the comment area.

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?

I cannot help you, there. If you expect the workflow to be exactly the
same, I strongly suggest you never switch away from Bugzilla.

d) I cannot set labels on my test project for some reason.

You need to have the appropriate permissions to do so; it's probably a
test instance issue.

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.

I seriously doubt you were born with innate knowledge of Bugzilla -
even though Bugzilla's feature set is basically limited to what you
see in the page.


[@] ebassi []

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]