Add branchFormat support for Jira issues#937
Open
kazimzaidi wants to merge 1 commit intoiloom-ai:mainfrom
Open
Add branchFormat support for Jira issues#937kazimzaidi wants to merge 1 commit intoiloom-ai:mainfrom
kazimzaidi wants to merge 1 commit intoiloom-ai:mainfrom
Conversation
Allow Jira users to configure a custom branch naming template
via issueManagement.jira.branchFormat in settings.json. The
template supports {ticketId} and {slug} variables, producing
branches like "print-1234-fix-deps-bug" instead of the default
"feat/issue-PRINT-1234__fix-deps-bug" format.
Changes:
- Add TemplateBranchNameStrategy and slugify utility
- Add branchFormat to Jira settings schema (both v1 and v2)
- Wire branchFormat through JiraIssueTracker -> IssueTracker
interface -> LoomManager -> BranchNamingService
- Expose branchFormat on LinearService for parity
- Add comprehensive tests for template strategy
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
branchFormatconfiguration option for Jira issue management, enabling custom branch naming templatesTemplateBranchNameStrategywith{ticketId}and{slug}variable substitutionbranchFormatthrough the full pipeline: settings schema → JiraIssueTracker → IssueTracker interface → LoomManager → BranchNamingServicebranchFormaton LinearService for parity (was already in schema but unused)Motivation
Jira users often have branch naming conventions tied to their ticket IDs (e.g.,
PRINT-1234-fix-deps-bug). The current hardcodedfeat/issue-{number}__{slug}format doesn't support this. Linear already hadbranchFormatin its schema (though unused) — this completes the feature for both providers.Configuration
{ "issueManagement": { "provider": "jira", "jira": { "branchFormat": "{ticketId}-{slug}" } } }il start PRINT-1234→ branch name:print-1234-fix-deps-bugTest plan
branchFormatin.iloom/settings.jsonand runil startwith a Jira ticket🤖 Generated with Claude Code