Can't mark inaccessible bug dependent on a regression it caused

RESOLVED FIXED

Status

()

bugzilla.mozilla.org
General
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: bz, Assigned: glob)

Tracking

Production

Details

Attachments

(1 attachment)

Until I was cced on bug 1203078, I could not add it as a dependency of bug 1205741 (a regression it caused).

This is pretty user-hostile; if someone has gone to the trouble of finding that a restricted bug caused a regression, I see no reason to prevent them from flagging that in Bugzilla.  Especially now that for most people doing triage most security bugs are restricted.
Flags: needinfo?(glob)
(Assignee)

Comment 1

2 years ago
this is asking for bug 141593 to be reverted - there were security concerns that resulted in the current check.
it's likely the landscape has changed a lot since then, so i think it should be ok to lift this restriction.

i'll raise this as a discussion point in our next meeting.
Flags: needinfo?(glob)
(Assignee)

Comment 2

2 years ago
we'd probably want to lift this restriction for users with canconfirm/editbugs, not everyone.
Note that for my purposes I don't need to be able to _remove_ dependencies, only add them.  And really only in one direction.

Of course if we had an explicit "X is a regression caused by Y" flag, I'd just need to be able to set that flag... ;)
(Assignee)

Comment 4

2 years ago
we discussed this in the meeting -- we'll do this limited to users with editbugs.
Assignee: nobody → glob
(Assignee)

Comment 5

2 years ago
Created attachment 8667907 [details] [diff] [review]
1205748_1.patch
Attachment #8667907 - Flags: review?(dylan)
Comment on attachment 8667907 [details] [diff] [review]
1205748_1.patch

Review of attachment 8667907 [details] [diff] [review]:
-----------------------------------------------------------------

r=dylan
Attachment #8667907 - Flags: review?(dylan) → review+
(Assignee)

Comment 7

2 years ago
To ssh://gitolite3@git.mozilla.org/webtools/bmo/bugzilla.git
   200cbd8..42270ff  master -> master
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.