Microsoft Project Server | Targetprocess - Visual management software
Microsoft Project Server
work Items

One-way and two-way synchronization:

  • Task
  • Epic
  • Feature
  • User Story
  • Task
  • Bug
  • Request
  • Test plan
  • Test Plan Run

Allocating the proper resources to a project is hard enough without having to worry about whether or not the data you’re working accurately reflects the reality of your teams. Organizations that use both Targetprocess and Microsoft Project Server will usually have a critical need to connect the two systems. With the Tasktop's Integration Hub, it's possible to enable both one-way  and two-way integration in order to connect planning and execution.


Every integration case is unique, because you have to map your own special set of fields and work structure. If you’re interested, please check with us via to get started with a demo.  

Possible use cases:
  • Project Managers build and manage high-level plans in Microsoft Project Server, while developers and other roles work in Targetprocess. Integrating the tools provides visibility into high-level goals for Targetprocess users, and details about progress and implementation specifics for Project Server users.
  • Some organizations may prefer to use a combination of Project Portfolio Management tools. They may use Microsoft Project Server for project management and Targetprocess for in-depth planning and visualization. Integrating the two and possibly adding other tools to the mix would certainly speed up the whole development cycle.
  • If your QA team is working in Targetprocess while developers and other teams work in Microsoft Project Server, integrating the tools will allow Project Server users to see aggregated data on the status of work items and any time spent in Targetprocess, and vice versa.