All instances of Bugzilla::Object should have ->create() and ->update() implemented

NEW
Unassigned

Status

()

--
enhancement
14 years ago
4 years ago

People

(Reporter: timello, Unassigned)

Tracking

(Depends on: 1 bug, {meta})

2.19.3
Dependency tree / graph

Details

(Whiteboard: [roadmap: 4.0])

Attachments

(3 attachments, 1 obsolete attachment)

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050405 Firefox/1.0 (Ubuntu package 1.0.2)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050405 Firefox/1.0 (Ubuntu package 1.0.2)

Step 2: Write/Validation Functions
We need methods and/or subroutines for validations and database persistence.
All related routines about inserts, updates, deletes and validations for those
routines have to be implemented at this bug.

Reproducible: Always

Steps to Reproduce:

Updated

14 years ago
Assignee: administration → timello
Status: UNCONFIRMED → NEW
Ever confirmed: true
(Reporter)

Updated

14 years ago
Depends on: 294160
(Reporter)

Updated

14 years ago
Blocks: 293524

Comment 1

14 years ago
I think we should split validation and DB-persistence into separate bugs.
Target Milestone: --- → Bugzilla 2.22
Version: unspecified → 2.19.3
(Reporter)

Comment 2

14 years ago
Created attachment 186497 [details] [diff] [review]
removed functions from 294160.
(Reporter)

Comment 3

14 years ago
Created attachment 187147 [details] [diff] [review]
make_product_group routine.

This routine belongs to Product.pm.
(Reporter)

Updated

14 years ago
Attachment #186497 - Attachment is obsolete: true
(Reporter)

Updated

14 years ago
Attachment #186497 - Attachment is obsolete: false
(Reporter)

Updated

13 years ago
Assignee: timello → gabriel
Assignee: gabriel → batosti

Comment 4

13 years ago
Created attachment 195411 [details] [diff] [review]
batosti_v1

an initial version.
Attachment #195411 - Flags: review?(LpSolit)

Comment 5

13 years ago
Created attachment 195461 [details] [diff] [review]
batosti_v2

more things for the Product.pm
Attachment #195411 - Attachment is obsolete: true
Attachment #195461 - Flags: review?(LpSolit)

Updated

13 years ago
Attachment #195411 - Flags: review?(LpSolit)

Comment 6

13 years ago
bug 299753 should be fixed first, and objects should be used instead of old
code. This bug should not be a simple copy and paste from editproducts.cgi into
Product.pm.
Depends on: 299753

Comment 7

13 years ago
Comment on attachment 195461 [details] [diff] [review]
batosti_v2

r- per my previous comment. And please remove the corresponding code from
editproducts.cgi (after the blocker is fixed).
Attachment #195461 - Flags: review?(LpSolit) → review-

Updated

13 years ago
No longer blocks: 293524
Depends on: 293524

Updated

13 years ago
Depends on: 313122

Updated

13 years ago
Depends on: 313123

Updated

13 years ago
Depends on: 313125

Updated

13 years ago
Depends on: 313129

Updated

13 years ago
Depends on: 313126

Comment 8

13 years ago
The trunk is now frozen to prepare Bugzilla 2.22. Enhancement bugs are retargetted to 2.24.
Target Milestone: Bugzilla 2.22 → Bugzilla 2.24

Comment 9

12 years ago
We are in "soft freeze" mode to prepare 3.0 RC1.
Target Milestone: Bugzilla 3.0 → Bugzilla 3.2

Updated

12 years ago
Whiteboard: [roadmap: 3.2]

Updated

12 years ago
Keywords: meta
Summary: Step 2 (RW): implement validations and database persistence functions for Product.pm, Component.pm Classification.pm, Milestones.pm and Version.pm. → All instances of Bugzilla::Object should have ->create() and ->update() implemented

Updated

11 years ago
Depends on: 355838

Comment 10

11 years ago
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

Updated

11 years ago
Whiteboard: [roadmap: 3.2] → [roadmap: 4.0]

Updated

10 years ago
Depends on: 454251

Updated

10 years ago
Assignee: batosti → administration

Updated

9 years ago
Depends on: 415541

Comment 11

6 years ago
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

Updated

4 years ago
Target Milestone: Bugzilla 5.0 → ---
You need to log in before you can comment on or make changes to this bug.