Closed Bug 428406 Opened 18 years ago Closed 16 years ago

contrib/bz_webservice_demo.pl fails with --product_name (Product.get_products doesn't accept product names)

Categories

(Bugzilla :: WebService, defect)

3.0.3
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 385283

People

(Reporter: LpSolit, Unassigned)

References

Details

bz_webservice_demo.pl fails when called with --product_name defined as it tries to call Product.get_product() with the product name as argument, but this API has been rename to Product.get_products() (plural!) and now only accepts a list of product IDs. I think the current API is wrong! You have no way to guess the ID of a product, and passing a product name to the API makes *much more* sense than passing a list of IDs. So Product.get_products() should still be able to accept a (list of) product name(s) alongside with accepting a list of product IDs. I consider this as a regression as it was working fine (i.e. in a "logical" manner) till 2.23.3. We should fix this API before 3.2 RC1, IMO. We should also fix it on the 3.0 branch as it won't break its current behavior.
There was never a stable release of Bugzilla that had the ability to get products by name, as far as I can see. I'm surprised that's the case--we definitely should allow it. However, it would be an enhancement. If it gets done quickly, I might take it for 3.2, but 3.0 is not open for enhancements (unless you can show me some stable release that had this functionality).
Severity: normal → enhancement
Keywords: regression
Target Milestone: Bugzilla 3.0 → Bugzilla 4.0
(In reply to comment #1) The demo script being broken is a bug, not an enhancement!
Ah, yes, that's a bug, you're right.
Severity: enhancement → normal
Target Milestone: Bugzilla 4.0 → Bugzilla 3.0
(In reply to comment #1) > There was never a stable release of Bugzilla that had the ability to get > products by name, as far as I can see. I'm surprised that's the case--we > definitely should allow it. However, it would be an enhancement. If it gets > done quickly, I might take it for 3.2, but 3.0 is not open for enhancements > (unless you can show me some stable release that had this functionality). For the background for the current interface, you may want to review the history of bug 356816 :-)
The Bugzilla 3.0 branch is now locked to security bugs and dataloss fixes only. This bug doesn't fit into one of these two categories and is retargetted to 3.2 as part of a mass-change. To catch bugmails related to this mass-change, use lts081207 in your email client filter.
Target Milestone: Bugzilla 3.0 → Bugzilla 3.2
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Target Milestone: Bugzilla 3.2 → ---
You need to log in before you can comment on or make changes to this bug.