Enabling Multiple Ticket Integrations between Trackers and Git and SVN

Ticket integration is one of our most popular features at CloudForge.  It allows a developer to update a ticket in a tracker with the commit message, or status of the ticket.  It is simple, powerful, and widely used.

Currently, to set this up, you create a CloudForge project; make sure you have at least one source control service (Git or SVN) and a tracker service (TeamForge, Trac …).  You also need to make sure that Ticket Integration is enabled for this project.  Although this works well for most cases, customers sometime want to have multiple SVN or Git repositories sharing a single tracker.  For example, an Engineering team may have multiple SVN repositories, but share the same tracker for project tracking.

CloudForge has now made this easier!  You can now have many CloudForge Projects, each with its own SVN or Git repositories, and by specifying the tracker project that you want to integrate with, you can now use the ticket integration from multiple repositories to a single tracker.

For example, in the above diagram, from any of the repositories 1 – 3, you can use the following ticket integration syntax to integrate with Project4’s Tracker1.

svn ci –m “work in progress [s:trac, t:2, p:project4]”

S: is the type of tracker, t: specifies the ticket ID, p: specifies the project short / system name.  With this enhanced capability, you can even share tracker integration (Jira, Rally … integration) from multiple repositories using the same ticket integration syntax.

Tagged with: , , , , , , ,
Posted in CloudForge, Git, Subversion

Leave a Reply

Your email address will not be published. Required fields are marked *

*