DevOps Article

Projects and Git Integrations

Last updated: March 11, 2026 4 min read Intermediate

Projects and Git Integrations

Projects let you group issues under a shared key prefix and connect Git repositories for automatic activity tracking.

Creating a Project

  1. Navigate to DevOps > Projects in the sidebar.
  2. Click New Project.
  3. Enter a name and a unique project key (uppercase letters and numbers, 2 to 10 characters). The key cannot be changed after creation.
  4. Optionally set a project lead, default issue type, default assignee, and a default branch naming pattern.
  5. Click Create to save.

Connecting a Repository

  1. Open a project and go to its Settings page.
  2. Click Add Connection.
  3. Select a provider (GitHub, GitLab, or Bitbucket).
  4. Enter the repository URL, a display name, and your access token.
  5. Click Connect. ISO Mate validates the token and detects read/write capabilities.

Token Requirements

Each provider uses a different token type. ISO Mate automatically detects read/write capabilities from the token scopes.

GitHub

GitHub supports two token types:

  • Classic Personal Access Token: In GitHub from your profile icon, go to Settings > Developer settings > Personal access tokens > Tokens (classic). Select the repo scope for full access (branches, PRs, commits). For read-only access to public repos, select public_repo.
  • Fine-grained Personal Access Token: In GitHub from your profile icon, go to Settings > Developer settings > Personal access tokens > Fine-grained tokens. Select the target repository, then set Contents to Read and write and Pull requests to Read and write for full access. For read-only, set Contents to Read-only.

GitLab

GitLab supports Personal Access Tokens and Project Access Tokens:

  • Personal Access Token: Go to User Settings > Access > Personal Access Tokens. Select the api scope for full access. For read-only, select read_api and read_repository.
  • Project Access Token: Go to Project > Settings > Access Tokens. Select the api scope and assign at least the Developer role for write access.

Bitbucket

Bitbucket Repository Access Tokens are the recommended option (App Passwords are deprecated as of September 2025):

  • Repository Access Token: Go to Repository Settings > Security > Access Tokens. Select the pullrequest:write scope for full access (includes branch creation, push, and PR management). For read-only, select the repository scope.
  • Workspace Access Token: Go to Workspace Settings > Security > Access Tokens. Same scopes apply but the token works across all repositories in the workspace.

Viewing Git Activity

Once a repository is connected, ISO Mate syncs branches, commits, and pull requests every 15 minutes. It matches issue keys (e.g., PROJ-42) in branch names, commit messages, and PR titles to link activity to the correct issues.

Open any issue and scroll to the Git Activity section to see linked branches, commits, and pull requests grouped by repository. Each item links to the provider’s web interface.

Creating Branches and Pull Requests

From the issue detail page, click Create Branch to create a new branch in one or all connected repositories. The branch name is pre-populated with the issue key and summary. Click Create MR/PR to open a draft pull request with the issue key in the title.

Pull requests can be marked as drafts using the checkbox in the dialog. For GitLab, the “Draft:” prefix is automatically added to the title. For GitHub, the native draft flag is set. Toggle the checkbox to add or remove the draft prefix from the title.

These actions require write access on the repository token. If a connection has read-only access, the buttons will be disabled with a tooltip explaining the requirement.

Managing Linked Branches and Pull Requests

Each branch and pull request in the Git Activity section has an action menu (three-dot icon) with the following options:

  • Unlink Branch: Removes the link between the branch and the issue. The branch remains in the repository.
  • Delete Branch: Permanently deletes the branch from the remote repository and removes all local records. Only available when the connection has write access. A confirmation dialog is shown before proceeding.
  • Unlink Pull Request: Removes the link between the pull request and the issue. The pull request remains open on the provider.
  • Close Pull Request: Closes the pull request on the remote repository and updates the local status. Only available for open pull requests. A confirmation dialog is shown before proceeding.

Managing Connections

On the project settings page, each connection shows its status (Active, Error, or Syncing) and capability level (Read Only or Read & Write). You can edit a connection to update its token, revalidate a connection in error state, or delete a connection entirely.

Feature

Was this article helpful?