314423 - Unable to set dependency on a bug that I cannot access

Status: VERIFIED INVALID

(Bugzilla :: Creating/Changing Bugs, defect)

Description

[Boris Zbarsky [:bzbarsky]]

I was filing bug 314421, and wanted to mark it dependent on a bug I cannot access (bug 311765), since it's clear from comments elsewhere that the "fix" for that bug is causing my problems.  Unfortunately, not only can I not _read_ bug 311765, but I can't even mark bugs depending on it.  While this is convenient for people who might want to avoid knowing about the breakage bug 311765 caused, I'd think that in most cases we want to allow setting such a dependency.  Without that and without a way to look at the bug, there is really no way to get the attention of the people involved so that they can fix the regression.

Comment 1

[A. Karl Kornel]

(In reply to comment #0)
> Unfortunately, not only can I not _read_ bug 311765, but I can't even mark bugs depending on it.  

Due to the landing of bug 141593, I'd say this behavior is to be expected.

> Without that and without a way to look at the bug, there is really
> no way to get the attention of the people involved so that they can fix the
> regression.

I'd suggest checking on IRC for someone who can set the dependency for you.  For more information, check out <http://www.bugzilla.org/support/>.

Comment 2

[Joel Peshkin]

comment 1 is correct.  You are not supposed to be able to slap a dependency on a bug you cannot see.  However, someone who can see it (possibly whoever made the comment to you that the other bug was relevent to your problem) could do so.

I looked at the 2 bugs and it was not sufficiently obvious for me to do it for you.  I don't think we want anybody slapping dependencies on bugs blindly.

Comment 3

[Boris Zbarsky [:bzbarsky]]

> I'd suggest checking on IRC for someone who can set the dependency for you. 

Given the usual response times on IRC, this is not an option.  I just don't have the time to waste on that sort of thing; I'm trying to use bugzilla for a real use here (tracking Gecko bugs).

> I looked at the 2 bugs and it was not sufficiently obvious for me to do it for
> you.

And there is that problem too -- once you find someone, you have to convince them to pretty please set an obvious dependency for you....

Comment 4

[Christian :Biesinger (don't email me, ping me on IRC)]

this is clearly not worksforme... comments sound like it is supposed to be invalid. fixing that.