Export bug_tracker APIs for upstream components
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Bryce Harrington |
Bug Description
The Launchpad API should provide routines to make it easy to access information about a bug watch.
Some rough brainstorming (subject to change extensively):
* getProductsForB
* getComponentsFo
* getRemoteProduc
* getComponentFor
* setComponentFor
* setSourcePackag
Perhaps others...
This bug is a work-item for the following LEP: https:/
Related branches
- Gavin Panella (community): Approve
-
Diff: 574 lines (+271/-31)10 files modifiedlib/canonical/launchpad/interfaces/_schema_circular_imports.py (+17/-2)
lib/canonical/launchpad/webapp/batching.py (+18/-0)
lib/canonical/launchpad/webapp/configure.zcml (+8/-0)
lib/lp/bugs/browser/bugtracker.py (+15/-1)
lib/lp/bugs/browser/configure.zcml (+12/-1)
lib/lp/bugs/configure.zcml (+4/-1)
lib/lp/bugs/interfaces/bugtracker.py (+30/-15)
lib/lp/bugs/model/bugtracker.py (+34/-2)
lib/lp/bugs/tests/test_bugtracker_components.py (+131/-7)
lib/lp/testing/factory.py (+2/-2)
description: | updated |
tags: | added: story-bugzilla-component-link |
Changed in malone: | |
assignee: | nobody → Bryce Harrington (bryceharrington) |
importance: | Undecided → High |
status: | New → In Progress |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in malone: | |
status: | Fix Committed → Fix Released |
Several of these just fell out of the basic implementation of the model/interface stuff, so I'll just need to doublecheck that they're getting exported properly and can be accessed from scripts.
* getProductsForB ugtracker - Available as BugTracker: component_ groups rProduct - Available as BugTrackerCompo nentGroup: components t(remote_ bug) - see below SourcePackage - will be solved by bug #644794
* getComponentsFo
* getRemoteProduc
* getComponentFor
* setComponentFor SourcePackage - will be solved by bug #644794 eForComponent - will be solved by bug #644794
* setSourcePackag
getRemoteProduct() might not be needed. For existing bug watches, they *should* already have the product included with the watch. For upstream bugs not associated with a bug watch, I think we don't care about providing a lookup function there. So I don't think we need anything done for this routine.