Issue Trackers

Tower automatically turns issue numbers in commit messages into clickable links. When you reference issues like #123 or PROJ-456 in your commits, Tower detects them and creates direct links to your issue tracker.

Custom Configuration

Smart Defaults If your repository is connected to GitHub, GitLab, or other hosting services, Tower automatically infers the URL pattern and prefix. Custom Configuration is only needed for custom issue trackers.

You can configure issue tracker URLs and prefixes either globally (for all repositories) or per repository (to override global settings).

Global Configuration

In the Tower Settings window, navigate to the Integration tab to find the Issue Tracker section.

Clicking Edit will open a dialog where you can customize the following:

• Issue Tracker URL
• Issue Number Prefix

Issue Tracker URL

Enter the URL for your issue tracking service with {ISSUE_NUMBER} as a placeholder:

https://github.com/owner/repository/issues/{ISSUE_NUMBER}

You can also use {OWNER} and {REPOSITORY} placeholders.

Issue Number Prefix

Define the pattern to identify issue numbers in commits:

• # for GitHub-style like #123
• PROJ- for Jira-style like PROJ-456
• Any custom prefix up to 20 characters

The prefix is case-sensitive.

Repository-Specific Configuration

You can override global settings for individual repositories in Repository Settings > General > Issue Tracking.

Repository-specific settings take precedence over global configuration.

Supported Services

Tower works with any web-based issue tracker.

Autodetected Services

Tower attempts to automatically infer issue tracker settings for repositories connected to:

• GitHub & GitHub Enterprise
• GitLab & GitLab Self-Managed
• Bitbucket Cloud & Bitbucket Server
• Azure DevOps
• GitSwarm

Manual Configuration

For other issue trackers, configure the URL pattern and prefix manually:

Jira Cloud

Use your project key as prefix (e.g., PROJ-) with URL https://yourcompany.atlassian.net/browse/PROJ-{ISSUE_NUMBER}

Linear

Use your team key as prefix (e.g., TEAM-) with URL https://linear.app/your-workspace/issue/{ISSUE_NUMBER}

Custom Issue Trackers

Any web-based issue tracker can be configured as long as the URL includes {ISSUE_NUMBER} placeholder.

Using Issue Links

Tower automatically detects issue numbers in commit messages and converts them into clickable links in the commit detail view. Hover over any detected issue number to see the full URL before clicking.

Frequently Asked Questions

Does this work without configuration?

If your repository is connected to one of the autodetected services mentioned above, Tower automatically infers the appropriate URL pattern and prefix. Manual configuration is only needed for other issue trackers.

Can I use different issue trackers for different repositories?

Yes. You can configure issue tracker settings globally, per repository, or both.

Can I use special characters in my prefix?

Yes. Tower automatically escapes special characters, so prefixes like [ISSUE] or {TICKET:} work correctly.

Why does URL validation fail?

Ensure your URL includes {ISSUE_NUMBER} and uses http:// or https://. Only {OWNER} and {REPOSITORY} placeholders are supported.

How does Tower populate {OWNER} and {REPOSITORY}?

Tower extracts these from your repository's default remote (typically "origin").