Projects in ISO Mate group issues under a shared key prefix and let you connect Git repositories so branches, commits, and pull requests are tracked against the right issues. You manage projects from the Projects page in the DevOps group of the left sidebar, and you connect repositories from each project’s settings. Once connected, ISO Mate keeps repository activity in sync automatically.
Creating a project
- Open Projects: In the left sidebar, expand the DevOps group and select Projects.
- Start a new project: Select New Project.
- Enter the basics: Give the project a name and a key of 2 to 10 uppercase letters or numbers. The key is fixed at creation and cannot be changed afterward.
- Set optional defaults: You can choose a project lead, a default issue type, a default assignee, and a default branch naming pattern.
- Create: Select Create to save. ISO Mate opens the project settings so you can connect a repository next.
Issues created under the project take its key as their prefix, so a project keyed PROJ produces PROJ-1, PROJ-2, and so on.
Connecting a repository
- Open project settings: From the Projects list, open a project’s settings using its settings action.
- Add a connection: In the Repositories card, select Add Connection.
- Pick a provider: Choose GitHub, GitLab, or Bitbucket.
- Enter the details: Provide the repository URL, a display name, and an access token.
- Connect: Select Connect. ISO Mate validates the token and detects whether the connection has read only or read and write access.
Provider access tokens
Each provider uses its own token type, and ISO Mate reads the token scopes to decide whether the connection can write. The dialog shows guidance for the selected provider, summarized here.
GitHub
Use a classic personal access token with the repo scope, or a fine grained token with Contents and Pull requests both set to Read and write. For read only access, a token with Contents set to Read is enough.
GitLab
Use a personal or project access token with the api scope for full access, or the read_api and read_repository scopes for read only access.
Bitbucket
Create a repository access token with the pullrequest:write scope for full access, which includes branch and pull request creation, or the repository scope for read only access.
Viewing git activity
Once a repository is connected, ISO Mate syncs branches, commits, and pull requests every 15 minutes and matches issue keys, for example PROJ-42, found in branch names, commit messages, and pull request titles to link the activity to the right issue.
Open any issue and go to its Git Activity section to see the linked branches, commits, and pull requests grouped by repository, each with a link out to the provider. You can also refresh the section on demand with its sync action.
Creating branches and pull requests
From an issue’s Git Activity section, select Create Branch to create a branch in a connected repository, with the branch name prefilled from the issue. Select Create MR/PR to open a pull request that carries the issue key in its title.
The pull request dialog starts as a draft and adds a “Draft:” prefix to the title. Toggle the Mark as Draft checkbox to add or remove that prefix. Both actions need a connection with write access, so on a read only connection the buttons are disabled with a tooltip explaining why.
Managing linked branches and pull requests
Each branch and pull request in the Git Activity section has an action menu with the following options.
- Unlink Branch: Removes the link between the branch and the issue. The branch stays in the repository.
- Delete Branch: Deletes the branch from the remote repository after a confirmation. This appears only when the connection has write access.
- Unlink Pull Request: Removes the link between the pull request and the issue. The pull request stays open on the provider.
- Close Pull Request: Closes the pull request on the provider after a confirmation, and is available for open pull requests.
You can also copy a branch name or a ready made checkout command from each branch to move quickly into your local workflow.
Managing connections
On the project settings page, each connection shows its status (Active, Error, or Syncing) and its capability (Read Only or Read and Write). You can edit a connection to update its token, revalidate a connection that is in an error state, or delete a connection entirely.