Trying to view an attachment to a bug requiring group membership should not give the same error as viewing the bug itself

NEW
Unassigned

Status

()

Bugzilla
Attachments & Requests
P3
minor
13 years ago
10 years ago

People

(Reporter: timeless, Unassigned)

Tracking

({ue})

Details

(URL)

(Reporter)

Description

13 years ago
steps:
1. log out.
2. follow a link to attachment 192279 [details]
2' Access Denied
	  	
You are not authorized to access bug #304224. To see this bug, you must first 
log in to an account with the appropriate permissions.

3. click the "log in to an account" link
4. log in
4' bug 304224
4` attachment 192279 [details]

Updated

13 years ago
Severity: normal → minor
OS: Windows XP → All
Hardware: PC → All
Summary: Trying to view a classified attachment should not give the same error as viewing a classified bug → Trying to view a private attachment should not give the same error as viewing a private bug

Comment 1

13 years ago
Please don't say "private" as "private" attachments and "private" comments are
another feature. Maybe "restricted"?

/me was going to invalidate this bug due to that.
(Reporter)

Comment 2

12 years ago
i suppose some expected results might be useful, although it seemed obvious.

Access Denied to attachment 192279 [details]
	  	
You are not authorized to access attachment 192279 [details]. To see this attachment, you must first log in to an account with the appropriate permissions.
Summary: Trying to view a private attachment should not give the same error as viewing a private bug → Trying to view an attachment to a bug requiring group membership should not give the same error as viewing the bug itself
(Reporter)

Updated

12 years ago
Keywords: ue

Comment 3

10 years ago
this doesn't need any UE evaluation, You're 100% correct timeless. The fix is if you go to an attachment URL that you don't have access to, the error should say you don't have access to the attachment not to the bug. 

Help users recognize, diagnose, and recover from errors
    Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.

Updated

10 years ago
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.