https://bugs.documentfoundation.org/show_bug.cgi?id=101513
--- Comment #31 from Philippe Cloutier <[email protected]> --- Greetings V Stuart Foote (and apologies to others), (In reply to V Stuart Foote from comment #30) > (In reply to Philippe Cloutier from comment #29) > > > I am not sure what you mean by “REOPEN”, but FIXED is not correct, as this > > ticket does not report a bug. In general, status is reverted when a solution > > is reverted (although there was indeed a long time until reversion in this > > case). > > Nope, simply not how we handle it for this project on this TDF Bugzilla. We > open a NEW issue "ticket" with reference(s) as/if needed. I work[ed] on hundreds of projects, I was not talking specifically about TDF Bugzilla, although both scenarios also occur here (see e.g. bug #89319). > > > As to that the correct way in Bugzilla to ref another issue is to simply > > > enter it as "bug + number" so "bug 172275", distinct from the comments in > > > gerrit or git where for example a tdf#172275 that gerrit accepts as a link > > > back to the Bugzilla issue. > > > Besides being longer, that would be incorrect; #172275 is not a bug, but > > rather a ticket. > > Again, just entering the #12345 has no meaning and is not BZ filter parsed > in this instance as hyperlink to a hopefully relevant issue. Redmine will automatically link “#12345”, but that's not even what I did; I wrote “ticket #172275”, which has little ambiguity in TDF Bugzilla’s context. > The "bug <12345>" syntax does that, and it makes the QA review and workflows > much > more efficient. I struggle to understand what you mean by that, but if it's that helpful, I recommend you document these benefits and/or complete the parser to cover the most common terms. > So of course thankyou for contributing with some insight, but there are some > norms you'll need to get used to. Thanks again for the suggestion, but the main norm that needs getting used to here is… respect. If you sponsor my future contributions to TDF, I will be happy to format my comments whichever way you prefer. With a small extra, you might even convince me to call a non-bug “bug #999999”. Until then though, if you remain involved in CBPP ITSs, you will not only have to get satisfied with *promoting* your preferences rather than imposing them, but endure suboptimalities in your colleagues’ comments (and the resulting frustration) which go well beyond the absence of links. In particular on TDF Bugzilla, which has very limited support for links. One way to start showing such respect which I'd advise you to focus on is to designate your colleagues correctly, which in my case―as for the vast majority of Philips―requires a single “l”: “Philippe”. -- You are receiving this mail because: You are the assignee for the bug.
