Open
Bug 372017
(bz-field-security)
Opened 18 years ago
Updated 1 years ago
Field-level security
Categories
(Bugzilla :: Bugzilla-General, enhancement, P1)
Tracking
()
NEW
People
(Reporter: mkanat, Unassigned)
References
(Depends on 4 open bugs, Blocks 3 open bugs)
Details
(Keywords: meta, Whiteboard: [roadmap: 4.0])
Once we've done the appropriate re-architecture, we will want to have field-level security. This consists of:
* Controlling who can see certain fields
* Controlling who can change certain fields
And eventually, probably:
* Controlling who can see/set certain values
This would basically replace the long bunch of code we currently have in Bugzilla::Bug::check_can_change_field.
Reporter | ||
Updated•18 years ago
|
Priority: -- → P1
![]() |
||
Comment 1•18 years ago
|
||
Note bug 90619. A part of your request, if not all, is already part of this bug.
Reporter | ||
Updated•18 years ago
|
Alias: bz-field-security
Reporter | ||
Updated•18 years ago
|
Reporter | ||
Comment 3•18 years ago
|
||
This has become a meta-bug for tracking this feature.
Keywords: meta
Reporter | ||
Updated•17 years ago
|
Whiteboard: [roadmap: 4.0]
Target Milestone: --- → Bugzilla 4.0
![]() |
||
Comment 6•12 years ago
|
||
We are going to branch for Bugzilla 4.4 next week and this bug is either too invasive to be accepted for 4.4 at this point or shows no recent activity. The target milestone is reset and will be set again *only* when a patch is attached and approved.
I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else.
Target Milestone: Bugzilla 4.4 → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•