26 lines
1.1 KiB
Markdown
26 lines
1.1 KiB
Markdown
# 03 Ticket Branch Discovery by Ticket Key
|
|
|
|
## Goal
|
|
|
|
Show branches related to a ticket by matching configured repository branches against the ticket key prefix.
|
|
|
|
## Requirements
|
|
|
|
- Add a branches section to the ticket detail view.
|
|
- For each configured project repository connection, identify branches whose names start with the ticket key.
|
|
- A matching branch must be shown on the ticket when its name starts with the exact ticket key, for example `AUTH-42-...`.
|
|
- Present matches in a way that makes the repository source clear.
|
|
- The first implementation may use direct fetches or a simple cache, but it must not require a large background sync system.
|
|
|
|
## Acceptance Criteria
|
|
|
|
- A ticket with key `AUTH-42` shows branches such as `AUTH-42-login-form`.
|
|
- Branches that do not start with the ticket key are not shown.
|
|
- If multiple connected repositories contain matching branches, the ticket shows matches from each relevant repository.
|
|
|
|
## Out of Scope
|
|
|
|
- Commit listing
|
|
- Branch creation from inside KanbanGit
|
|
- Cross-ticket branch disambiguation beyond exact ticket-key prefix matching
|