The mechanism xProcess provides for implementing such integrations is the Workflow Server. This can monitor the tracker system as well as changes within the xProcess data source and trigger actions when specific changes are detected. How does this work out in practice? Here's a brief summary of a current integration with a leading tracking tool.
- The tracker is used to create, modify and review issues
- xProcess is used for planning and executing the confirmed issues
- When issues are confirmed, work is planned by instantiating the correspondingpattern (say for a bug-fix) in the appropriate xProcess project. It is the user setting the status to “confirmed” that triggers the transfer into the plan.
- Updates made to the data in the tracker may cause an alert or update in xProcess and vice versa.
- When sub-tasks close in xProcess, the plan status in tracker is updated by the Workflow Server. For example states like: Specified
,Code complete, and Accepted correspond to particular subtasks being completed and closed in the project.
- If an issue is deleted or closed in the tracker, data is transferred to xProcess and may cause an alert to the project manager or other flags to be set in the data.
- Viewing the task in xProcess allows data from the tracker screens to be viewed (and updated) directly. Reverse links also possible.
- The issue in tracker and its corresponding task or tasks in xProcess are independent objects but with linked lifecycles that are controlled and synchronized through the Workflow Server.