The overal objective is import part of an existing bugzilla base into a Tuleap tracker:

• Import is done bug per bug
• An imported bug is called hereafter artifact-proxy
• An artifact-proxy is viewed in read-only mode and with only a part of the information of the original bug:
  • ID
  • title
  • description
  • status
  • product
  • component
  • hardware
• An artifact-proxy has a link to the original bug in bugzilla
• An artifact-proxy is updated on regular basis (cron?) with its remote counter-part
  • Modifications are kept in Tuleap changests (?)
• An artifact-proxy doesn't have remote history nor user's comments
• A given user can request update of artifact-proxy "in real time" (click on "Update from remote" button)
  • It's not done by default because of latency
• In a given tracker, their can be a mix of local, regular artifacts (modifiable) and artifact-proxies
• No permissions are checked, we consider that the remote is accessible anonymously (open source for instance)

Use cases

• As a tracker admin, I can define that my tracker can create artifact-proxy from a bugzilla base. I have a special page where I can define the mapping between Tuleap Trackers fields and Bugzilla fields
• As a tracker user, I can create an artifact-proxy. The only field I have is to set the ID of the remote bug in bugzilla. The artifact is actually created in background after a little while when Tuleap backend had the possibility to fetch the data.
• Every nights (frequency to be defined) the artifact-proxy are updated automatically if their counter-part changed.
• As a tracker user, I can also do a "massive import" from bugzilla either:
  • Based on a bugzilla query
  • Or CSV import
  • In both case, there is an hard limit of imported artifacts (eg. 100) to avoid mis-usage.

Questions and limits

• Special fields:
  • Do we need to import "blocks/depends on" fields ?
    • If yes, should it be imported as other "artifact-proxy" or should it reference the remote bug only (no "Artifact links" in Tuleap world)