Supported trackers
The row appears in the sidebar’s ISSUES section when one of the repository’s remotes is on a supported provider. Jira, if connected, appears in the same section. Turn the whole section on or off with Show Issues in Settings → General or from the sidebar’s context menu.
Bitbucket Data Center and Azure DevOps Server (on-premises) are not supported.
Connect an account
Commit+ uses the Git provider account you already connected for the remote’s host. If no account is connected, the issues screen shows Connect…; if the saved account no longer works, it shows Reconnect. Both open your provider accounts. Some trackers need extra access:- GitHub — For an organization’s repository, the organization must grant Commit+ access. Use Manage Organization Access… on the issues screen, or Grant Organization Access on GitHub in the account sheet.
- Bitbucket — The repository’s issue tracker must be turned on. The API token needs the
read:issue:bitbucketandwrite:issue:bitbucketscopes, and you must enter your Atlassian Email in the account sheet. The email stays on this Mac with the token. - Azure Boards — The personal access token needs the Work Items scope.
Browse issues
Select the tracker row in the ISSUES section. The list shows open issues by default; Azure Boards shows work items from the repository’s project.- Search by title or number.
- State — Open, Closed, or All.
- Show — All, Assigned to Me, or Created by Me.
- Remote — appears when more than one remote has a supported tracker, for example a fork with an
upstreamremote. - Reset Filters clears the filters, and Refresh reloads the list.
Create, comment, close, and reopen
- Click New Issue… to create an issue with a title and a Markdown description. On Azure Boards, also choose the work item type.
- Type in Add a comment at the bottom of the details panel and click Comment.
- Use Close Issue or Reopen Issue in the details panel’s actions.
Start a branch from an issue
Use Create Branch… in the details panel or the row’s context menu. Commit+ suggests a name made from the issue number and title, such as42-fix-login-crash. When Git Flow is set up for the repository, you can start a Git Flow topic instead, as with Jira issues.

