Repository Mapping

Link your GitHub repositories to ClickUp spaces for automatic task detection.

Overview

Repository mapping tells Jasper which ClickUp spaces to search when detecting task IDs in your pull requests. Each repository can be mapped to one or more spaces.

Configure Repository Mapping

Set up your repository mappings in the ClickUp settings page.

Open ClickUp Settings

Setting Up a Mapping

  1. In the ClickUp settings page, find Repository Mappings
  2. Click Configure next to the repository you want to set up
  3. Select the ClickUp workspace (if you have multiple)
  4. Choose one or more spaces to search for tasks
  5. Configure the task ID pattern (default: CU-[a-zA-Z0-9]+)
  6. Choose where to detect task IDs (branch name, PR title, description, commits)
  7. Click Save Mapping

How Task Linking Works

When a pull request is opened or updated, Jasper scans the PR metadata to find ClickUp task IDs:

Source Example
Branch Name feature/CU-abc123-add-login
PR Title [CU-abc123] Add user login feature
PR Description Closes CU-abc123
Commit Messages feat: implement login CU-abc123

Custom Task ID Patterns

You can customize the regex pattern used to detect task IDs for each repository mapping. Common patterns include:

  • CU-[a-zA-Z0-9]+ - Standard ClickUp task IDs (default)
  • #[0-9]+ - Numeric-only task IDs
  • PROJ-[0-9]+ - Project-prefixed IDs

Detection Sources

Choose which parts of the PR to scan for task IDs:

Source Description Recommended
Branch Name The git branch name (e.g., feature/CU-123-login) Yes
PR Title The pull request title Yes
PR Description The pull request body/description Optional
Commit Messages All commit messages in the PR Optional

Tip: We recommend enabling at least "Branch Name" and "PR Title" for reliable task detection. Scanning commit messages can be useful but may slow down detection for large PRs.

Multiple Spaces

You can map a repository to multiple ClickUp spaces. This is useful when:

  • Your team works across multiple projects in different spaces
  • You have separate spaces for different types of work (features, bugs, etc.)
  • Tasks may be moved between spaces during their lifecycle

Jasper will search all mapped spaces when detecting task IDs.

Next Steps

ClickUp Overview Auto Comments