Export bug_tracker APIs for upstream components

Bug #617699 reported by Bryce Harrington
6
This bug affects 1 person
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):

  * getProductsForBugtracker - List of products supported by a given bugtracker
  * getComponentsForProduct - List of components for a given product in a remote bugtracker
  * getRemoteProduct(remote_bug) - Given a remote bug id that exists in launchpad, identify its product
  * getComponentForSourcePackage - Identify the remote bug tracker component that corresponds to a source package

  * setComponentForSourcePackage - allows programmatic linking of component and source package
  * setSourcePackageForComponent - allows programmatic linking of component and source package

Perhaps others...

This bug is a work-item for the following LEP: https://dev.launchpad.net/LEP/BugzillaComponents

Related branches

Bryce Harrington (bryce)
description: updated
tags: added: story-bugzilla-component-link
Bryce Harrington (bryce)
Changed in malone:
assignee: nobody → Bryce Harrington (bryceharrington)
importance: Undecided → High
status: New → In Progress
Revision history for this message
Bryce Harrington (bryce) wrote :

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.

  * getProductsForBugtracker - Available as BugTracker:component_groups
  * getComponentsForProduct - Available as BugTrackerComponentGroup:components
  * getRemoteProduct(remote_bug) - see below
  * getComponentForSourcePackage - will be solved by bug #644794

  * setComponentForSourcePackage - will be solved by bug #644794
  * setSourcePackageForComponent - will be solved by bug #644794

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.

Revision history for this message
Launchpad QA Bot (lpqabot) wrote : Bug fixed by a commit
Changed in malone:
milestone: none → 10.11
tags: added: qa-needstesting
Changed in malone:
status: In Progress → Fix Committed
Bryce Harrington (bryce)
tags: added: qa-ok
removed: qa-needstesting
Curtis Hovey (sinzui)
Changed in malone:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.