Open Bug 624408 Opened 10 years ago Updated 5 years ago
When cloning a bug custom fields are copied even if the reporter doesn't have permission to set them, doesn't allow for editing
Not sure what this bug is about but I think you have it created accidentally.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 620218
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
According to Boris on Bug 620218 I set Wanted flags when I created that bug. All I did was "clone", bugzilla set the wanted flags. (note to self, don't use clone again ;-)
Severity: critical → normal
Status: REOPENED → NEW
This is a dupe, though I can't find the dupe right now.
Assignee: mozillamarcia.knous → nobody
Component: Bugzilla: Keywords & Components → Bugzilla: Other b.m.o Issues
QA Contact: timeless → other-bmo-issues
I've been searching, trying to find a bug filed for this but can't find it. I don't think this is a bmo bug, it's a Bugzilla bug, so moving. The issue is that all custom fields are pre-populated with the data from the cloned bug (which is technically correct) without regard for the reporter's credentials and permissions. They can't be edited either.
Assignee: nobody → create-and-change
Component: Bugzilla: Other b.m.o Issues → Creating/Changing Bugs
Product: mozilla.org → Bugzilla
QA Contact: other-bmo-issues → default-qa
Summary: bugzilla sets 'wanted' flags when you clone a bug. → When cloning a bug custom fields are copied even if the reporter doesn't have permission to set them, doesn't allow for editing.
Whiteboard: DUPEME → Summary in comment 4
Version: other → unspecified
(In reply to comment #4) > don't think this is a bmo bug, it's a Bugzilla bug, so moving. No, this is not a Bugzilla bug. Everyone is free to edit custom fields on bug creation, independently of his privs. The pseudo-flags discussed in this bug do not exist upstream. It's a bmo customization.
Assignee: create-and-change → nobody
Component: Creating/Changing Bugs → Bugzilla: Other b.m.o Issues
Product: Bugzilla → mozilla.org
QA Contact: default-qa → other-bmo-issues
Version: unspecified → other
Can you please re-verify this is still a problem? A fix was pushed out recently that fixed custom field values not displaying properly for enter_bug.cgi which could have also caused this problem. Dave
Still an issue, I just cloned bug 637542 (didn't actually submit) and the final+ blocking was the value in the blocking2.0 field. If you want me to actually submit a test bug, I can do that too (then again, so can you).
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
Still an issue with current code. Will need to investigate further.
You need to log in before you can comment on or make changes to this bug.