#219: Integration with Development Task Trackers
Отредактирована: сегодняIntegration Capabilities
You can connect a task tracker to Swarmica to link tasks with requests. Currently, the following trackers are available for connection:
Upon request, the following is connected:
- Kaiten
With the integration active, you can search for tasks in the tracker using the search field in the upper right corner of the request page. By keywords, a task is found:
If a task is crucial to the request, an employee can attach the task to the request using the Add to Request option.
After attachment, the task is located on the right side of the request page. Directly from the request page, without going to the tracker, you can see the title, text, and all parameters of the request: type, tags, status. At the bottom of the block, you can see the name of the employee who added the task to the request and the time since the task was added.
The trash can icon
can be used to unattach a task from a request if it was attached by mistake or has become irrelevant. The refresh icon
can be used to update the data of the attached task.
The icon may, depending on the type of tracker, be located in the lower right corner of the task block or next to the status:
When a task is closed, an event will be added to the request associated with that task, and the responsible person will receive a notification by email.
Integration with Trackers
To integrate with your tracker, go to Settings - Task Trackers:

On the page that opens, click on your tracker's name.
Connecting Gitlab
- Tracker URL - the Gitlab address from the browser's address bar.
- Additional Fields - optional fields from the tracker that should be included in the task for its transfer to Swarmica.
- API Token - created in Gitlab in User Settings - Access tokens, be sure to check read_api! To create tasks from Swarmica, the api and Reporter role are also required.
- Timeout - the time period in seconds during which Swarmica will contact the tracker in the absence of an immediate response. The default is 30 seconds, it is not recommended to change this parameter except for special requirements of your DevOps or network administrator.
- Active - enable the slider to activate the integration.
Don't forget to save the settings!
Gitlab block in the request:
Connecting Jira
- Authorization Type: token or basic. For basic type, authorization by username and password is required, unlike token authorization.
- User - Jira username through which requests will be made. Not required for filling in for token authorization type.
- Tracker URL - Jira address from the browser's address bar.
- Additional Fields - optional fields from the tracker that should be included in the task for its transfe