Closed Bug 467173 Opened 16 years ago Closed 11 years ago

No warning when attaching with flag request to no-right users.

Categories

(Bugzilla :: Attachments & Requests, defect)

defect
Not set
minor

Tracking

()

RESOLVED DUPLICATE of bug 372539

People

(Reporter: himorin, Unassigned)

Details

When requesting flags to some no-right users (users who are rejected by flag's grant group), Bugzilla returns error message and prohibit the change.
Bug when attaching file with flag request, Bugzilla doesn't return error and attaches the file with deleting requestee. (so, flag status will be '?' from wind.)

Bugzilla should return error or at least show some warning message.
No, no error should be thrown. That was the old behavior, and we decided it was better to let the attachment going through, but remove the requestee. But I agree that the same message as when editing an attachment should be displayed.
Severity: normal → minor
Flags: testcase?
Target Milestone: --- → Bugzilla 3.2
(In reply to comment #1)
> No, no error should be thrown. That was the old behavior, and we decided it was
> better to let the attachment going through, but remove the requestee.

ok.
Agree with this dicision.

> But I agree that the same message as when editing an attachment should be displayed.

So, display warning with using global/messages.html.tmpl?
(In reply to comment #2)
> So, display warning with using global/messages.html.tmpl?

Yes, we already have a message for this. See what happens when you edit an existing attachment.
Bugzilla 3.2 is restricted to security bugs only. Moreover, this bug is either assigned to nobody or got no traction for several months now. Rather than retargetting it at each new release, I'm clearing the target milestone and the bug will be retargetted to some sensible release when someone starts fixing this bug for real (Bugzilla 3.8 more likely).
Target Milestone: Bugzilla 3.2 → ---
Flags: testcase?
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.