Best regards.
--
View this message in context:
http://nabble.documentfoundation.org/FDO-Permissions-tp4007909p4010328.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
On Fri, 2012-09-28 at 10:33 -0700, bfo wrote:
> This could be done on per project basis. Unfortunately with
Oh ! if we know that this is easy to turn on on a per product basis
(ie. a simple bugzilla setting just for our product); then that is
trivial to get turned on.
Can you co
org/docs/en/html/groups.html.
Best regards.
--
View this message in context:
http://nabble.documentfoundation.org/FDO-Permissions-tp4007909p4009925.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
chael Meeks wrote
> Generally we try to avoid things that
> need freedesktop's bugzilla customising specifically for our one product
> though.
attitude (and the same time paying for enabling build-in features) you can't
do much.
Best regards.
--
View this message in co
.
Julien
--
View this message in context:
http://nabble.documentfoundation.org/FDO-Permissions-tp4007909p4007976.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.fre
Apologies in advance about not including Julien's message, I'm still not
quite sure how to deal with direct email response vs. nabble response so
here is my response to not needing it.
I agree right now there isn't truly a need but as we grow I think that
recognizing who is QA and who isn't will b
ok at the author of
comments, you know enough quickly if a member of QA responded about this.
In brief, IMHO I don't think there's a need to change something about this
in bugtracker but perhaps I'm wrong.
Julien
--
View this message in context:
http://nabble.documentfoundation
What about adding some kind of whiteboard status (I knowmorenot
good), that is like "verified and prioritized by a member of QA", then in
the future when we're cleaning the NEW bugs and prioritizing them we know
when an experienced user has already done the triaging (vs. the user just
tryin
Hi Joel,
On Mon, 2012-09-17 at 08:56 -0700, Joel Madero wrote:
> I know that this is a touchy subject and needs a lot of discussion
> but, how difficult is it to make it so you need permissions to change
> priority and severity of a bug? My goal is to at least "kind of" deal
> with priorities in t
Hi All,
I know that this is a touchy subject and needs a lot of discussion but, how
difficult is it to make it so you need permissions to change priority and
severity of a bug? My goal is to at least "kind of" deal with priorities in
the coming months but it's pretty much impossible if a regular u
10 matches
Mail list logo
