Hi Folks,
I have a couple of problems and proposals that I'd like to discuss for bugs.centos.org:
PROBLEM 1: Currently when a user reports an issue it's very difficult for them to know where to route things properly. The confusion seems to be between projects and categories. For example, Ci.centos.org Ecosystem Testing is the category under the Buildsys project that's supposed to be used for both infrastructure issues and new account requests. It's not immediately obvious that the user needs to select the Buildsys project to get there though. If they do make it that far, but forget to choose the Ci.centos.org ecosystem testing category , it may get assigned by default to someone who are active in CentOS but outside of maintaining the CICO infra (sorry alphacc and range!).
PROPOSAL: Move CentOS CI to it's own "Project" so that it shows up in the dropdown list, and allow us to segment CI requests from SIG requests.
PROBLEM 2: In the Buildsys project, once someone reports and issue, they can no longer update it (ex: if they chose the wrong category, or no longer have the issue and would like to close it). In a few projects like Buildsys (and CICO) it makes sense to allow these folks a little freedom in modifying some of the bug fields.
PROPOSAL: For the Buildsys and CICO projects -only- allow Reporters to Close, Reopen, and Update their own issues. This would leave the Distro and SIG projects unaffected.
I can make these changes if we're all happy. Are there any objections?
-- Brian Stinson CentOS Infrastructure Team
On 27/11/2018 19:24, Brian Stinson wrote:
PROPOSAL: Move CentOS CI to it's own "Project" so that it shows up in the dropdown list, and allow us to segment CI requests from SIG requests.
+1
PROPOSAL: For the Buildsys and CICO projects -only- allow Reporters to Close, Reopen, and Update their own issues. This would leave the Distro and SIG projects unaffected.
are you sure about reporters ( ie almost everyone ) not being able to reopen existing cases ?
I am ok with Close and Update
regards,
On Nov 27 21:32, Karanbir Singh wrote:
On 27/11/2018 19:24, Brian Stinson wrote:
PROPOSAL: Move CentOS CI to it's own "Project" so that it shows up in the dropdown list, and allow us to segment CI requests from SIG requests.
+1
PROPOSAL: For the Buildsys and CICO projects -only- allow Reporters to Close, Reopen, and Update their own issues. This would leave the Distro and SIG projects unaffected.
are you sure about reporters ( ie almost everyone ) not being able to reopen existing cases ?
Yep, on the buildsys project if a bug gets set to Resolved or higher the Reporter cannot reopen the bug. There are 2 ways to fix that, allow reporters to set the bug to any state in the workflow (bad), or use the explicit "Reporter can reopen" permission (good).
--Brian
On 27/11/18 22:49, Brian Stinson wrote:
On Nov 27 21:32, Karanbir Singh wrote:
On 27/11/2018 19:24, Brian Stinson wrote:
PROPOSAL: Move CentOS CI to it's own "Project" so that it shows up in the dropdown list, and allow us to segment CI requests from SIG requests.
+1
+1 here too
PROPOSAL: For the Buildsys and CICO projects -only- allow Reporters to Close, Reopen, and Update their own issues. This would leave the Distro and SIG projects unaffected.
are you sure about reporters ( ie almost everyone ) not being able to reopen existing cases ?
Yep, on the buildsys project if a bug gets set to Resolved or higher the Reporter cannot reopen the bug. There are 2 ways to fix that, allow reporters to set the bug to any state in the workflow (bad), or use the explicit "Reporter can reopen" permission (good).
--Brian
wfm
-
Brian Stinson -
Fabian Arrotin -
Karanbir Singh