Request for Bugzilla karma

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Request for Bugzilla karma

Arrigo Marchiori
Dear dev@ list,

could I please get permission to do a bit of Bugzilla administration?

I am subscribed with my own e-mail address and I would like to assign
bug 128424 to myself.

If possible, the version tag 4.1.9 should also be added.

Thank you in advance,
--
Arrigo

http://rigo.altervista.org

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Request for Bugzilla karma

Marcus (OOo)
Am 18.01.21 um 21:24 schrieb Arrigo Marchiori:
> could I please get permission to do a bit of Bugzilla administration?
>
> I am subscribed with my own e-mail address and I would like to assign
> bug 128424 to myself.

if added to the following BZ groups:

- canconfirm: Can confirm a bug or mark it a duplicate
- editbugs: Can edit all bug fields
- qa-team: Members of the AOO QA team

This should give you full access about BZ issues.

> If possible, the version tag 4.1.9 should also be added.

The "Target Milestone" can already be set to 4.1.9.

However, the tag for "Version" and "Last Confirmation in" is needed (and
actually) created when the release is published.

Marcus


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Request for Bugzilla karma

Peter Kovacs-3
In reply to this post by Arrigo Marchiori
On 18.01.21 21:24, Arrigo Marchiori wrote:
> I am subscribed with my own e-mail address and I would like to assign
> bug 128424 to myself.

Is it possible to keep [hidden email] in the loop?

I keep my overview of bugzilla through that mailinglist.

If you just assig the issue to you I think we will not receive any
notifications, and at least for me who does work on having an overview,
the issue drops out of my scope.

I am also fine if there is some sort of notification where the Issue is now.


All the Best

Peter

--
This is the Way! http://www.apache.org/theapacheway/index.html

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Request for Bugzilla karma

Andrea Pescetti-2
On 19/01/2021 Peter Kovacs wrote:
> On 18.01.21 21:24, Arrigo Marchiori wrote:
>> I am subscribed with my own e-mail address and I would like to assign
>> bug 128424 to myself.
> Is it possible to keep [hidden email] in the loop? ...
> If you just assig the issue to you I think we will not receive any
> notifications

You are right, and this should be fixed.

I believe that the issues mailing list is meant to receive notifications
for any bug changes. But it seems the latest changes to
https://bz.apache.org/ooo/show_bug.cgi?id=126369
(which was assigned to me even if Matthias did the work... thank you!)
were not sent to the issues list:
https://lists.apache.org/list.html?issues@...:2020-12

If I recall correctly, we relied on a "trick" that would set the "QA
contact" field for any new issues to the issues mailing list. Even if
the assignee is changed, the "QA contact" is not reset and this meant
the issues list received all notifications.

But I don't see it set even for issues recently created such as
https://bz.apache.org/ooo/show_bug.cgi?id=128420

Is there any Bugzilla configuration that must be fixed?

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Keep issues@ in bug reports [Was: Request for Bugzilla karma]

Arrigo Marchiori
Hello,

FWIW...

On Sun, Jan 24, 2021 at 09:10:51PM +0100, Andrea Pescetti wrote:

[...]
> If I recall correctly, we relied on a "trick" that would set the "QA
> contact" field for any new issues to the issues mailing list. Even if the
> assignee is changed, the "QA contact" is not reset and this meant the issues
> list received all notifications.
>
> But I don't see it set even for issues recently created such as
> https://bz.apache.org/ooo/show_bug.cgi?id=128420

Confirmed. My last report:
https://bz.apache.org/ooo/show_bug.cgi?id=128424
has empty "QA contact" and I cannot change it.

issues@ is the default "Assignee" and I cannot change it as well.

Best regards,
--
Arrigo

http://rigo.altervista.org

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Keep issues@ in bug reports [Was: Request for Bugzilla karma]

Marcus (OOo)
Am 25.01.21 um 09:15 schrieb Arrigo Marchiori:

> FWIW...
>
> On Sun, Jan 24, 2021 at 09:10:51PM +0100, Andrea Pescetti wrote:
>
> [...]
>> If I recall correctly, we relied on a "trick" that would set the "QA
>> contact" field for any new issues to the issues mailing list. Even if the
>> assignee is changed, the "QA contact" is not reset and this meant the issues
>> list received all notifications.
>>
>> But I don't see it set even for issues recently created such as
>> https://bz.apache.org/ooo/show_bug.cgi?id=128420
>
> Confirmed. My last report:
> https://bz.apache.org/ooo/show_bug.cgi?id=128424
> has empty "QA contact" and I cannot change it.
>
> issues@ is the default "Assignee" and I cannot change it as well.

IMHO we just ned to make sure that isues@ is either the assignee - this
works as long as nobody is taking over the issue for working on it - or
it's in the CC list. Then every update on the issue will be posted to
issues@.

I'm quite sure I've done it already, but I've enabled you for the
following BZ groups in BZ:

canconfirm: Can confirm a bug or mark it a duplicate
editbugs: Can edit all bug fields
qa-team: Members of the AOO QA team

Marcus


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Keep issues@ in bug reports [Was: Request for Bugzilla karma]

Arrigo Marchiori
On Tue, Jan 26, 2021 at 07:56:24PM +0100, Marcus wrote:

> Am 25.01.21 um 09:15 schrieb Arrigo Marchiori:
> > FWIW...
> >
> > On Sun, Jan 24, 2021 at 09:10:51PM +0100, Andrea Pescetti wrote:
> >
> > [...]
> > > If I recall correctly, we relied on a "trick" that would set the "QA
> > > contact" field for any new issues to the issues mailing list. Even if the
> > > assignee is changed, the "QA contact" is not reset and this meant the issues
> > > list received all notifications.
> > >
> > > But I don't see it set even for issues recently created such as
> > > https://bz.apache.org/ooo/show_bug.cgi?id=128420
> >
> > Confirmed. My last report:
> > https://bz.apache.org/ooo/show_bug.cgi?id=128424
> > has empty "QA contact" and I cannot change it.
> >
> > issues@ is the default "Assignee" and I cannot change it as well.
>
> IMHO we just ned to make sure that isues@ is either the assignee - this
> works as long as nobody is taking over the issue for working on it - or it's
> in the CC list. Then every update on the issue will be posted to issues@.

I understand.

> I'm quite sure I've done it already, but I've enabled you for the following
> BZ groups in BZ:
>
> canconfirm: Can confirm a bug or mark it a duplicate
> editbugs: Can edit all bug fields
> qa-team: Members of the AOO QA team

Confirmed! Thank you!

Best regards,
--
Arrigo

http://rigo.altervista.org

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Keep issues@ in bug reports [Was: Request for Bugzilla karma]

Andrea Pescetti-2
In reply to this post by Marcus (OOo)
Marcus wrote:
> IMHO we just ned to make sure that isues@ is either the assignee - this
> works as long as nobody is taking over the issue for working on it - or
> it's in the CC list. Then every update on the issue will be posted to
> issues@.

Even though I can't really find it in older issues like
https://bz.apache.org/ooo/show_bug.cgi?id=125000
(so I might remember something wrong) I believe we had some Bugzilla
configuration that would set the QA Contact to issues@ by default. This
way we didn't have any strange tricks to do when taking/assigning an
issue, as the QA Contact is a separate field.

Maybe you can find something in the Bugzilla configuration that defines
the default QA contact? I believe this address receives notifications
too, so setting it to issues@ would solve the problem.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Keep issues@ in bug reports [Was: Request for Bugzilla karma]

Marcus (OOo)
Am 26.01.21 um 22:57 schrieb Andrea Pescetti:
> Marcus wrote:
>> IMHO we just ned to make sure that isues@ is either the assignee -
>> this works as long as nobody is taking over the issue for working on
>> it - or it's in the CC list. Then every update on the issue will be
>> posted to issues@.
>
> Even though I can't really find it in older issues like
> https://bz.apache.org/ooo/show_bug.cgi?id=125000
> (so I might remember something wrong)

right, issues@ is not the assignee or in the CC list.
When looking into the history of the issue then 2014 the assignee was
changed away from issues@.

 > I believe we had some Bugzilla
> configuration that would set the QA Contact to issues@ by default. This
> way we didn't have any strange tricks to do when taking/assigning an
> issue, as the QA Contact is a separate field.
>
> Maybe you can find something in the Bugzilla configuration that defines
> the default QA contact? I believe this address receives notifications
> too, so setting it to issues@ would solve the problem.

Sorry, not in BZ itself. I've looked into the admin settings but cannot
find a suitable option.

On "https://bz.apache.org/ooo/enter_bug.cgi" there is also no automated
assignee.

Marcus


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Keep issues@ in bug reports [Was: Request for Bugzilla karma]

Andrea Pescetti-2
Marcus wrote:
> Am 26.01.21 um 22:57 schrieb Andrea Pescetti:
>> Maybe you can find something in the Bugzilla configuration that
>> defines the default QA contact? ...
> Sorry, not in BZ itself. I've looked into the admin settings but cannot
> find a suitable option.

I believe our old (and I don't know how old!) configuration was using
these settings:
https://www.bugzilla.org/docs/2.18/html/components.html

"The Owner, QA Contact, and Reporter will get email when new bugs are
created in this Component and when these bugs change. Default Owner and
Default QA Contact fields dictate the default assignments".

Now, I've never administered Bugzilla so I have no idea where one can
set those (or even if this is enabled in our current instance), but if
that can help...

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Keep issues@ in bug reports [Was: Request for Bugzilla karma]

Marcus (OOo)
Am 30.01.21 um 12:17 schrieb Andrea Pescetti:

> Marcus wrote:
>> Am 26.01.21 um 22:57 schrieb Andrea Pescetti:
>>> Maybe you can find something in the Bugzilla configuration that
>>> defines the default QA contact? ...
>> Sorry, not in BZ itself. I've looked into the admin settings but
>> cannot find a suitable option.
>
> I believe our old (and I don't know how old!) configuration was using
> these settings:
> https://www.bugzilla.org/docs/2.18/html/components.html
>
> "The Owner, QA Contact, and Reporter will get email when new bugs are
> created in this Component and when these bugs change. Default Owner and
> Default QA Contact fields dictate the default assignments".
>
> Now, I've never administered Bugzilla so I have no idea where one can
> set those (or even if this is enabled in our current instance), but if
> that can help...

thanks for the hint. In the BZ version we are using it's still possible
to set a default assignee.

However, also here everything is as it should. Every component has
issues@ as default assignee.

Marcus


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]