Open Bug 355838 (bz-object) Opened 18 years ago Updated 10 years ago

Most Bugzilla/*.pm modules should use Bugzilla::Object

Categories

(Bugzilla :: Bugzilla-General, enhancement)

2.23
enhancement
Not set
normal

Tracking

()

People

(Reporter: LpSolit, Unassigned)

References

(Depends on 2 open bugs, Blocks 2 open bugs)

Details

(Keywords: meta, Whiteboard: [roadmap: 4.0])

Most Bugzilla modules (if not all) should use Bugzilla::Object methods to create objects and to add and edit data to the DB. And why not also to delete data and destroy objects.

This way, we would have a centralized way to interact with the DB and to create (lists of) objects very efficiently.

This also means that all CGI scripts should now use Bugzilla::* modules to handle data. But that's another and already filed bug. ;)
Whiteboard: [roadmap: 3.2]
Alias: bz-object
Keywords: meta
Depends on: 388251
Blocks: 297791
Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?", and either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.
Target Milestone: Bugzilla 3.2 → Bugzilla 4.0
Whiteboard: [roadmap: 3.2] → [roadmap: 4.0]
Depends on: 471871
Depends on: 593169
Depends on: 452887
No longer depends on: 286509
Depends on: 679516
We are going to branch for Bugzilla 4.4 next week and this bug is too invasive or too risky to be accepted for 4.4 at this point. The target milestone is set to 5.0 which is our next major release.

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 on time for 5.0.
Target Milestone: Bugzilla 4.4 → Bugzilla 5.0
Target Milestone: Bugzilla 5.0 → ---
You need to log in before you can comment on or make changes to this bug.