Open Bug 372017 (bz-field-security) Opened 17 years ago Updated 7 months ago

Field-level security

Categories

(Bugzilla :: Bugzilla-General, enhancement, P1)

enhancement

Tracking

()

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.
Priority: -- → P1
Note bug 90619. A part of your request, if not all, is already part of this bug.
Alias: bz-field-security
Depends on: 71519
Depends on: 71520
Depends on: 372976
Depends on: 372977
Blocks: 71519, 71520, 90619
No longer depends on: 71519, 71520
Depends on: 372978
This has become a meta-bug for tracking this feature.
Keywords: meta
Depends on: 396600
Whiteboard: [roadmap: 4.0]
Target Milestone: --- → Bugzilla 4.0
Blocks: 353690
Blocks: 295338
Blocks: 369812
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.