884326 - Creating a bug blocking a bug that you don't have access to throws a nonsensical error

Status: NEW

(Bugzilla :: Creating/Changing Bugs, defect)

Description

[Patrick Cloke [:clokep]]

I just tried to create a bug on bugzilla.mozilla.org that blocked a bug I do not have authorization to view (I know what the bug is and I've seen the changeset, it made sense to link the two together). After pressing "Submit Bug" to create the bug I was brought to the " You are not authorized to access bug #xxxxx." page. Was my bug created? I have no idea.

My initial thought was that I had somehow gotten locked out of a bug that I filed, but that didn't make much sense. Eventually I realized that the bug hadn't been filed at all (and that I needed to go remove the bug I'm unauthorized to view from the blocklist).

This error seems like non-sense in this context, a better error could be thrown (at least telling me my bug hasn't been filed yet!)

Comment 1

[Frédéric Buclin]

I don't see how this error message is non-sense. You link your bug to a bug you don't have access to, and the error message tells you that you don't have access to that bug, which is accurate. If you get an error message, I doubt anyone would think that the operation succeeded.

Comment 2

[Patrick Cloke [:clokep]]

No, it is non-sense. It's unrelated to the operation I'm attempting (creating a bug). From the user's point of view they're not trying to read the bug that you're marking as blocked. After submitting a bug, I expect it to bring me back to the bug I just created.

If you can't create the bug because I don't have permission to read a different bug, let me know that specifically. It's bad UX.

I also assumed the bug # it was saying was the bug I had just created and not the bug I was trying to link to. (Any bug number with the same first 2 digits pretty much looks the same to me and I couldn't get more information, like the bug title, because I wasn't authorized!)