Add ticket-driven branch creation flow
This commit is contained in:
@@ -252,11 +252,21 @@ Initial expectations:
|
||||
- The first supported provider is Gitea.
|
||||
- Later providers should include GitHub and potentially GitLab.
|
||||
- Tickets will later expose branch and pull request sections.
|
||||
- The ticket branch section should eventually allow users to create a new branch directly from the ticket detail view.
|
||||
|
||||
Ticket-to-Git matching rule:
|
||||
|
||||
- A branch or pull request belongs to a ticket when its branch name starts with the ticket key.
|
||||
|
||||
Branch creation expectations:
|
||||
|
||||
- The ticket detail view may expose a branch creation action inside the branch section.
|
||||
- The branch creation flow should let the user choose from all project-linked repositories.
|
||||
- Repository choices remain visible even when the current user has no matching personal Git connection.
|
||||
- If the user lacks access to the selected repository, branch creation fields must stay disabled and guide the user to their Git connection settings.
|
||||
- The suggested branch name should start from the ticket key plus a title-derived suffix and remain editable before creation.
|
||||
- The UI should validate that the proposed branch name is syntactically acceptable and not already taken before creation is submitted.
|
||||
|
||||
Example:
|
||||
|
||||
- Ticket key: `AUTH-42`
|
||||
|
||||
Reference in New Issue
Block a user