Skip to main content
Video tutorial · 1:38

Tracker

The Tracker is the issue tracker built into Merge Pilot. It holds change approvals for companies that do not use Jira, or that want their change approvals kept inside Merge Pilot, and it can hold ordinary tasks that merge requests reference as work items. This section covers using it day to day; connecting it is described in Built-in tracker.

For a short overview of what it is for, see the Built-in tracker feature page.

Where it is​

Tracker is in the left menu, in the Work group, for every role. It opens the board of the company's first tracker project (projects are sorted by name); the project picker switches to another. A platform admin works in the company selected in the company switcher.

Pages of the tracker:

PageWhat it shows
Board and listA project's issues as columns by state, or as a table. See Board and list
Issue pageOne issue: its fields, comments, history and merge request. See Issue page
Project settingsA project's states, transitions, approving and rejecting states, issue types and custom fields. Company admins only. See Workflow and project settings
Archived projectsArchived projects and their issues, read-only. See Archived projects

The Dashboard shows a card Active tracker issues: the company's issues in states of the categories To do and In progress, with the number in Done states below it.

Two kinds of project​

Every tracker project has a Mode, chosen when it is created and never changed afterwards:

Mode (label in the UI)API valueWhat it is forWho creates its issues
VCSvcsChange approvals. A built-in tracker connection points to a VCS-mode project, and Merge Pilot opens a change approval there for each change that needs oneMerge Pilot only. People cannot create issues in it
ManualmanualOrdinary tasks, which merge requests can reference as work itemsPeople, with Create issue
VCS modeManual mode
Starting statesOpen, In Progress, Approved, Done, RejectedOpen, In Progress, Done
Starting movesOpen → In Progress, Approved or Rejected; In Progress → Approved or Rejected; Approved → DoneOpen → In Progress or Done; In Progress → Done
Approving and rejecting statesApproved and Done approve; Rejected rejectsNone (not shown in its settings)
Starting issue typesChange approval (default), Task, BugTask (default), Bug, Feature
Starting custom fieldsCode Reviewer, Tester and six review check boxes that must be ticked before Approved (see Workflow). Start without the review fields when creating the project leaves them out (API no_custom_fields, or custom_fields for your own); fields can be added later in the project's settingsNone, unless the project is created with its own (API custom_fields)
AssigneeSet by Merge Pilot; people cannot change it in the trackerAnyone may assign the issue
Summary and descriptionWritten by Merge Pilot from the tracker settings' templates; not edited on the issue pageEdited on the issue page

A project is created on the tracker page (New project, or Create project when the company has none) or, for a VCS-mode project, from the connection dialog (Create tracker project, see Built-in tracker):

Field (label in the UI)Allowed values
Project nameAny text, required
Prefix2 to 10 upper-case letters and digits, starting with a letter (prefix must start with a letter), required, unique within the company (an archived project keeps its prefix). Issue keys are the prefix and a number: CHG-1, CHG-2, … The prefix cannot be changed later
Description (optional)Any text
ModeManual (selected by default) or VCS

Custom fields given when a project is created (API custom_fields) are checked as in the project settings: each needs a key and a label, a known type, options for a select field, and a key no other field of the project has (see Custom fields). A project with a field that fails these checks is not created.

Who may do what​

ActionPlatform adminCompany adminPolicy managerAuditorUser
See projects, boards, issues and commentsYesYesYesYesYes
Create tracker projects, change their settings, archive themYesYesNoNoNo
Create issues in manual-mode projectsYesYesYesNoYes
Move issues between states, edit fields, commentYesYesYesNoYes
Assign issues of manual-mode projectsYesYesYesNoYes
Approve or reject a change approval in the tracker (move it to an approving or rejecting state)Assignee onlyAssignee onlyAssignee onlyNoAssignee only

The auditor reads everything and changes nothing (see The auditor is read-only): the issue page shows no Move to buttons, comment box or assignee search to an auditor, its switches cannot be changed, and cards on the board cannot be dragged.

Change approvals in the tracker​

When a merge request needs a change approval and the repository's VCS connection is linked to a built-in tracker connection, Merge Pilot opens it as an issue in a VCS-mode project. In short:

  • It is created in the project's first state, with the summary, description and fields the tracker settings give, a link to the merge request, and an assignee who may decide it (see Assignment).
  • Moving it to an approving state is an approval, to a rejecting state a rejection. Only its assignee may make these moves, never the merge request's author, and only after linking their account on the merge request's VCS in My profile. Merge Pilot then counts the decision under the change policy's rules (see Decisions made in the tracker).
  • Moving it out of an approving state withdraws the approval.
  • Merge Pilot moves it itself: back for the next approver, to the Reopen status after new commits, to the Merged status or Cancelled status when the merge request merges or closes, and to an approving or rejecting state when the change approval is decided in Merge Pilot.

The details are on Workflow and project settings, and the whole life of a change approval on Change approval lifecycle.

A change approval's link (on the merge request page and in the merge request's comments) opens the board of its tracker project; the issue is opened from there.

Work items​

Issues of the company's tracker projects can be referenced from merge requests as work items, when the merge request's tracker is the built-in tracker. Keys of the project where change approvals are created never count. See Tracker issues as work items.

What the tracker does not have​

  • No attachments.
  • No links between issues: a change approval is tied to its merge request, not to other issues.
  • Comments cannot be edited or deleted.
  • No webhooks and no notifications of its own.
  • A project cannot be deleted or brought back from the archive.

API​

All tracker endpoints act on the caller's company (a platform admin passes company_id).

EndpointWhat it doesWho
GET /api/v1/mptracker/projects (include_archived=true adds archived ones)List projectsAny role
GET /api/v1/mptracker/projects/{id}One project with its workflowAny role
POST /api/v1/mptracker/projects (name, prefix, mode, description)Create a projectCompany admin, platform admin
PUT /api/v1/mptracker/projects/{id}Change a project's settingsCompany admin, platform admin
DELETE /api/v1/mptracker/projects/{id}Archive a projectCompany admin, platform admin
GET /api/v1/mptracker/projects/{id}/board, GET /api/v1/mptracker/projects/{id}/issuesBoard and list (see Board and list)Any role
POST /api/v1/mptracker/projects/{id}/issuesCreate an issue in a manual-mode projectAny role but auditor
GET /api/v1/mptracker/issues/{id}, GET /api/v1/mptracker/issues/by-key/{key}One issueAny role
PUT /api/v1/mptracker/issues/{id}, POST /api/v1/mptracker/issues/{id}/transition, POST /api/v1/mptracker/issues/{id}/assignEdit, move, assign (see Issue page)Any role but auditor
GET and POST /api/v1/mptracker/issues/{id}/commentsRead and add commentsRead: any role; add: any role but auditor
GET /api/v1/mptracker/users?q=Active users of the company whose user name or display name starts with q (at most 50, 20 by default)Any role

Audit log​

ActionWhen
tracker_project_created, tracker_project_updated, tracker_project_archivedA project was created, its settings changed (with what changed), or it was archived
tracker_issue_createdSomeone created an issue in a manual-mode project
tracker_issue_updatedAn issue's summary, description, type or custom fields were changed
tracker_issue_transitionedSomeone moved an issue to another state
tracker_issue_assignedSomeone assigned an issue of a manual-mode project

Comments are not written to the audit log; change approvals' own actions are listed on Change approval lifecycle. See also Audit log.

Video tutorial

Short videos of this feature working on real GitLab and Jira projects. English audio, English and Turkish subtitles. All video tutorials →

Change Approvals Without JiraYouTube ↗