Hi James,
most of the comments have already been answered by Frank, but ...
James Mckenzie schrieb:
....
Issues that block a release, regardless of their category (be it a regression
or other) should be marked as a release-blocker. This should be separate
from the actual cause/category. Thus all issues that block a release can be
handled as separate entities rather than creating another issue just to handle
release blocker issues. Under no circumstances should the category be changed
just to mark an issue as a release blocker. Also, users should NOT be able to
set this field, but rather this action should be allowed only by a QA rep or higher.
As Frank already said, we are limited to Issue Tracker features and
cannot set so fine grained user rights.
But at least that needs to be stated as policy.
I'd revoke user privileges, if our policy is ignored although the user
has been warned. (This does not only apply to the blocker keyword but to
issue handling in genereal).
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
