Summary
Empty
push to Bugzilla Tuleap content

Bugzilla can still be a reference for tickets

Given a Tuleap tracker query (using REST API), push contents to Bugzilla:

  • All the fields that have the same name are synchronized. Eg. if there is a field "component" in Tuleap tracker, we will try to push to corresponding value to Bugzilla. If the value is not valid at Bugzilla side, the synchronisation will fail.
    • When the synchronization is done, we record Tuleap side the "Last Tuleap -> Bugzilla sync date" to have a point of reference for next sync
  • We use the XMLRPC API to do the replication
    • All changes will appear to come from one single user "Tuleap bot".
    • This user must have enough privileges to do the synchronization work.
  • When an artifact doesn't have a counterpart into bugzilla,
    • Then a new bug is created
    • The original Tuleap bug is updated with the corresponding bugzilla ID (for futur sync)

Note: as we use a Tuleap query to identify what needs to be replicated to Bugzilla, one can add a field to Tuleap tracker to identify which artifact should be replicated (public stuff) and which artifacts should be kept on Tuleap only (internal stuff).

Empty
Empty
Status
Empty
Canceled
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#9302
Manuel Vacelet (vaceletm)
2018-07-17 11:04
2016-07-01 17:15
9586

References
Referencing story #9302

Follow-ups