Users without editbugs can't close bugs as duplicate
Categories
(bugzilla.mozilla.org :: Bug Creation/Editing, defect)
Tracking
()
People
(Reporter: francesco, Assigned: dkl)
References
(Regression)
Details
(Keywords: regression)
I have the "editbugs" privilege, but I heard from a user who doesn't that they can't close a bug they filed as duplicate once they recognised the duplicate. The message they receive is:
You tried to change the Comment field , but only a user with the required permissions may change that field.
Additonal information:
You need permission to comment on this closed bug.
As a guess, the "closed bug" referred to in the message is the one that the existing bug should be duplicated to.
|
Assignee | |
Comment 1•1 year ago
|
||
This is due to the fact that duping a bug of another bug that is closed, the user is also 'editing' the closed bug in the process by adding the duplicate relationship. It is trying to add a comment to the closed bug. They would need editbugs to update the other bug that is closed as you mentioned.
We could add an exception to adding comments only for duplicates to be allowed by someone without editbugs, or the user would need to request someone to close their bug as a duplicate and a person with editbugs could do that change for them. I will look into what the best option would be in the code.
Thanks for considering the suggested improvement. If I'm not mistaken, user without editbugs can also not establish "See also", or they can only do it "unidirectionally", that means, in their bug A, bug B gets added as "See also", but in B, A doesn't get added. I'm not sure about other relationships, like "regressed by", etc.
|
|
Assignee | |
Comment 3•1 year ago
|
||
(In reply to Francesco from comment #2)
Thanks for considering the suggested improvement. If I'm not mistaken, user without editbugs can also not establish "See also", or they can only do it "unidirectionally", that means, in their bug A, bug B gets added as "See also", but in B, A doesn't get added. I'm not sure about other relationships, like "regressed by", etc.
Unfortunately there isn't way to add a unidirectional relationship unless of course you pt a URL to the other bug B in the URL field of bug A. So see_also, dependencies and regressions would all have the same issue as duplicates. Although duplicates are special in that they also try to add a comment to the other bug which is why the error.
There are more aspects to this. Today I tried to fill a "regressed by" field with the number of a security-restricted bug, and that fails claiming that there is no access to the security-restricted bug.
Description
•