Teams using GitHub Issues need a way to prioritize, track, and work on issues. Tasktop works with both hosted and on-premise GitHub Issues to let you establish both one-way or two-way integrations between GitHub and Targetprocess. When the same issue is represented in two systems, information on the artifact needs to be consistent everywhere. Teams also need to be able to communicate with the individuals who created the issue from both systems. Tasktop accommodates these needs.
Every integration case is unique, because you have to map your own special set of fields and work structure. If you’re interested in learning more, please contact us to get started.
Possible use cases
- If someone submits an issue in GitHub, the development team will see the issue and its metadata in Targetprocess. They can then prioritize and plan as they see fit, and communicate with the submitter via comments.
- When an issue in Targetprocess is completed, the corresponding issue in GitHub is closed, so everyone knows the work is completed.
Bitbucket + Targetprocess
CVS + Targetprocess
GitLab + Targetprocess
Vagrant + Targetprocess