Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      epic #4768 Bugzilla synchronisation with a Tuleap tracker
    Summary
    Bugzilla synchronisation with a Tuleap tracker
    Empty

    Executive summary

    This epic aims to provide a bi-directional synchronization between a bugzilla database and a Tuleap tracker.

    The objective is to be able to leverage as much as possible on Tuleap extended tracking capabilities while keeping the Bugzilla base as a reference. A typical use case would be a team that want to use Tuleap for developements (ie Agile features) while end users still interact with Bugzilla to report issues and feature requests.

    Open questions

    • What is the expected behaviour when a ticket is updated on both sides
      • Step 1: a bug from bugzilla is imported into Tuleap
      • Step 2: the bug is updated Tuleap side
      • Step 3: the bug is updated Bugzilla side
      • Step 4: What do we do synchronization is triggered ?
    • What  do we do with user informations when data are pushed to Bugzilla ?
      • In Tuleap we are able to replicate Bugzilla user database
      • But when we push data from Tuleap to Bugzilla (status updates, new comments, etc) what shall we do about the Tuleap author and Tuleap date ?

    Work to be done

    • Import from Bugzilla to Tuleap is already managed, this allow to create a Tuleap tracker out of a Bugzilla query (XML)
    • Update of Tuleap tracker (after initial import) to create new bugs and update the existing one. The import of new artifacts is already managed but there is a work to be done to deal with artifact update (likely need to keep a "last sync date" field in tracker, see gerrit #6106.
    • Push data from Tuleap to gerrit
      • There is a need to define a mapping (probably just based on the field names) and a list of fields that should be mapped
      • The comments can be replicated as well. They will be created on bugzilla by a system user for instance "Tuleap Bot" but will contain a text version of comment + user name + date
      • The push from Tuleap to Bugzilla can be done with XMLRPC API (see attachment)

    Relevant informations:

    • http://php.net/manual/fr/function.xmlrpc-encode-request.php
    • https://www.bugzilla.org/docs/4.4/en/html/api/Bugzilla/WebService.html
    Progress
    Empty
    Empty
    Canceled
    Details
    #4768
    dylan bowden (dylan)
    2018-07-17 11:04
    2013-08-14 09:51
    Attachments
    By Manuel Vacelet (vaceletm)
    (767 B)
    xmlrpc.php
    References
    Referencing epic #4768

    Artifact

    epic #4634 Replicate bugzilla content into Tuleap

    Display settings

    Follow-ups

    User avatar
    Manuel Vacelet (vaceletm)2016-07-01 17:31
    • Summary
      -Bugzilla synch with a Tuleap tracker 
      +Bugzilla synchronisation with a Tuleap tracker 
    User avatar
    Manuel Vacelet (vaceletm)2016-07-01 17:26
    • Description
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Manuel Vacelet (vaceletm)2016-06-30 18:50
    • Description
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Manuel Vacelet (vaceletm)2016-06-30 18:46
    • Description
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    • Attachments xmlrpc.php added
    User avatar
    dylan bowden (dylan)2013-08-14 10:35
    • Summary
      -BugZilla synch with a Tuleap tracker 
      +Bugzilla synch with a Tuleap tracker