From: Laszlo Ersek <lersek@redhat.com>
To: Michael Kinney <michael.d.kinney@intel.com>
Cc: edk2-devel-01 <edk2-devel@ml01.01.org>
Subject: bugzilla whining
Date: Fri, 29 Jul 2016 09:39:59 +0200 [thread overview]
Message-ID: <0a0d47fd-b214-a15e-1f3c-e33a19c74d91@redhat.com> (raw)
Hello Mike,
I got my first ever bugzilla whine today. It says "All of these bugs are
in the CONFIRMED state, and have not been touched in 7 days or more."
I'm not amused. :) I keep a very close eye on my BZs and I don't welcome
automated whines.
I checked the Bugzilla 5 documentation about whines:
http://bugzilla.readthedocs.io/en/5.0/administering/whining.html#whining
http://bugzilla.readthedocs.io/en/5.0/using/preferences.html?highlight=whine#permissions
http://bugzilla.readthedocs.io/en/5.0/administering/parameters.html?highlight=whine#email
I confirmed on my account (under Preferences | Permissions) that I have
the "bz_canusewhines" permission (--> "User can configure whine reports
for self"). However, when I go to Administration | Whining, it seems
that I can only create new whines -- I don't seem to have any personal
whines set up at the moment.
Which makes me think that this is a central default. Can we please make
it a personal setting instead?
Thank you,
Laszlo
next reply other threads:[~2016-07-29 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 7:39 Laszlo Ersek [this message]
2016-07-29 16:10 ` bugzilla whining Kinney, Michael D
2016-08-01 13:13 ` Laszlo Ersek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0a0d47fd-b214-a15e-1f3c-e33a19c74d91@redhat.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox