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 SettingsSetting Up a Mapping
- In the ClickUp settings page, open Repository Mappings
- Click Configure next to the repository you want to set up
- Select the ClickUp workspace (if you have multiple)
- Choose one or more spaces to search for tasks
- Configure the task ID pattern (default:
CU-[a-zA-Z0-9]+) - Leave PR Title ticked under Search In, and choose whether to tick Post review comments on tasks
- Click Save Mapping
How Task Linking Works
After Jasper reviews a pull request, it looks for task IDs in the pull request title, for example
[CU-abc123] Add user login feature. Each task it finds in the mapped spaces is linked to the pull request.
Custom Task ID Patterns
You can change the regex pattern used to detect task IDs for each repository mapping, but keep the default,
CU-[a-zA-Z0-9]+, which matches standard ClickUp task IDs. Jasper looks each match up by its ClickUp
task ID, so a pattern such as #[0-9]+ never links, and custom task IDs such as PROJ-123
aren't supported.
Search In
The mapping form has three Search In boxes: Branch Name, PR Title and PR Description. Only PR Title works today. Jasper doesn't store the branch name or the description of a pull request, so ticking those two boxes changes nothing. Put the task ID in the title.
The form also has a Sync PR status to tasks box. It does nothing: Jasper doesn't change a task's status when a pull request opens or merges.
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 links a task if it is in any of the mapped spaces.
Next Steps
- Auto Comments - Post review summaries to linked tasks
- PR Naming - Keep task IDs in your pull request titles