Built-in tracker
The MergePilot Tracker is the issue tracker built into Merge Pilot. A company without Jira, or one that wants change approvals kept inside Merge Pilot, connects it like any other tracker. It needs no URL, no credentials and no webhook: change approvals live in Merge Pilot, so their decisions are known right away.
Connection fields
Open the company's Connections tab, choose Add tracker connection and pick MergePilot Tracker as the Provider. Name and Active are described in Connections; there is no deployment type. The section MergePilot Tracker configuration has one field:
| Setting (label in the UI) | What it does | Default | Allowed values | Who can change it | API field |
|---|---|---|---|---|---|
| Tracker project | The tracker project the connection belongs to. Its states decide which moves approve or reject a change approval | none, required | A tracker project of the company in VCS mode that is not archived. Only VCS-mode projects can be linked to connections | Company admin | mergepilot_config.tracker_project_id |
Create tracker project creates a VCS-mode project without leaving the dialog:
| Field (label in the UI) | Allowed values |
|---|---|
| Project name | Any text, required |
| Prefix | 2 to 10 upper-case letters and digits, starting with a letter, required. Issue keys are the prefix and a number, for example CHG-12 |
| Description | Optional |
A new VCS-mode project starts with:
- states Open, In Progress, Approved, Done and Rejected; moves Open → In Progress, Approved or Rejected; In Progress → Approved or Rejected; Approved → Done;
- closing states Approved and Done, rejection state Rejected;
- issue types Change approval (the default), Task and Bug;
- user fields Code Reviewer and Tester, and review check boxes (DB, flow, load, log, quality and security review) that must be ticked before Approved.
These are changed in the tracker project's settings: see Workflow and project settings.
Test connection always succeeds for the built-in tracker. It takes no webhooks, so its row shows no webhook URL.
Tracker settings
The settings drawer (gear icon, Settings) has the same four sections as for Jira, without the Jira-only parts. Every setting is changed by a company admin; the API is PUT /api/v1/connections/{id}/tracker-settings.
| Section | Settings that apply | Differences from Jira |
|---|---|---|
| Project and types | Project, Issue type, Work item projects, Key pattern | Project is a tracker project's prefix (help: "Tracker project where change approval issues are created"); the connection's own tracker project is used when the prefix is its own or empty. Issue type lists that project's types; a type the project does not have falls back to the project's default type. There is no Link type and no Priorities |
| Statuses | Reopen status, Merged status, Cancelled status, Transition paths | There are no Closing statuses or Rejection statuses: the tracker project's terminal states decide which states approve or reject (any values sent through the API are dropped). Statuses are the project's states. A transition path lists states to pass through on the way to the target state, so their time is recorded; its steps have no fields |
| Templates | Summary template, Description template | Same variables as for Jira |
| Fields | Custom fields, Field mappings | Custom field values are filled in and given to the tracker project's own fields. There is no Check with Jira |
Project and Issue type are required, as for Jira.
How change approvals are created and decided
- A merge request needs a change approval. Merge Pilot creates an issue in the configured project, in the project's first state (Open by default), with the summary, description and fields from the settings, and assigns it to someone who may decide it. The assignee must have a Merge Pilot account; otherwise the change approval is not created.
- The issue carries a link to its merge request and the commit it covers.
- Only the assignee may move the issue to a closing or rejection state. The author of the merge request may never decide its change approval, and the person deciding must have linked their account on the merge request's VCS in My profile, so that Merge Pilot can tell them apart from the author.
- Moving the issue to a closing state approves the change; moving it to a rejection state rejects it. Merge Pilot then updates the merge gate.
- New commits, a merge, or closing the merge request move the issue to the Reopen status, Merged status or Cancelled status when they are set, as for Jira.
People are known to the built-in tracker by their Merge Pilot account, once they have linked their VCS account.
Video tutorial
Short videos of this feature working on real GitLab and Jira projects. English audio, English and Turkish subtitles. All video tutorials →