Integrating Tracker with other platforms

Developers have to use various platforms to build, test, and deploy their apps, among other things. You can use Tracker to find links to related resources or to issues hosted on other platforms, making cross-platform development more convenient. Use the Tracker API to send information from other platforms to Tracker. For more information about the Tracker API features, see the API reference.

You can transmit data from Tracker to another platform by sending HTTP requests via triggers.

Let's look at some examples of how you can link Tracker to other platforms.

Tracking the review code statusTracking the review code status

Suppose that a team uses a Bitbucket repo. When a developer creates a pull request in the repo, their colleagues review the code and accept or reject the pull request. If the pull request is accepted, the developer changes the issue status to Ready for Test; otherwise, to Needs improvement.

You can use the Tracker API to update issue statuses automatically based on the review results. However, this requires creating an intermediate service that would receive event information from Bitbucket, process it, and send requests to the Tracker API. Sample algorithm:

1. The developer makes a pool request and specifies the issue key in a comment. This way they identify the issue whose status needs to be updated.

2. In Bitbucket, you need to set up a web hook: when the reviewer accepts or rejects the pull request, Bitbucket sends an HTTP request to the intermediate service.

3. The intermediate service receives the HTTP request, determines the event type (whether the pool request was accepted or rejected), and retrieves the issue key from the comment left for the pool request.

4. The intermediate service then sends an issue status change request to the Tracker API. The request URL must include the issue key and the status key. You can find the status key in the Tracker settings on the Issue statuses tab.

   The request format is described in the API reference.

Linking a test bench to an issueLinking a test bench to an issue

Test benches are usually used to test new product features. If you are developing multiple features in parallel, it makes sense to create an independent test bench for each issue. To make it easy to find such a test bench, add a link to it to the issue. This can be done automatically using the Tracker API.

Let's assume your team has a script that automates test bench creation; this script uploads the application code from a specific issue branch, bundles it into a Docker image, and then uses this image to deploy a container on the server and starts it.

You can use the same script to include a link to the deployed test bench in the issue. To do this:

1. Create a new issue field named Bench link in Tracker.

2. When developing a new product feature, create a separate branch in the repository that must have the issue key specified in its name. This issue key is needed to send requests to the Tracker API.

3. Once the script has deployed the test bench, it sends a request to the Tracker API adding the bench address to the Bench link issue field. The request URL must include the issue key and the request body must include the key and the new field value. You can find the field key in the Tracker settings on the Fields tab.

   The request format is described in the API reference.

Sending notifications to a messengerSending notifications to a messenger

By using messengers, you can quickly notify your employees about important events. If a messenger has an API, you can use Tracker to set up a trigger that sends HTTP requests to the messenger API when certain events occur. For example, this might be handy when a severe error occurs in your queue.

To view examples for setting up triggers that send notifications to Slack and Telegram, see Integration with messengers.