Problem Statement:
Currently, the CLI for Jira creates branches with a fixed prefix ("feature") for all Jira ticket types, regardless of whether they are bugs, stories, or other types. While users can manually override this behavior by specifying a prefix using the --prefix configuration option, it is not convenient to do so for every ticket, especially when managing multiple ticket types simultaneously.
Proposed Solution:
Introduce a configuration variable (dynamic-branch-prefix or auto-branch-prefix) that, when active, will modify the branch naming convention to include the type of Jira ticket. For instance:
For bug tickets: Branches will be prefixed with "bugfix"
For story and task tickets: Branches will be prefixed with "feature"
For refactor tickets: Branches will be prefixed with "refactor"
This enhancement will improve branch naming consistency and aid in project organization.
Problem Statement:
Currently, the CLI for Jira creates branches with a fixed prefix ("feature") for all Jira ticket types, regardless of whether they are bugs, stories, or other types. While users can manually override this behavior by specifying a prefix using the --prefix configuration option, it is not convenient to do so for every ticket, especially when managing multiple ticket types simultaneously.
Proposed Solution:
Introduce a configuration variable (
dynamic-branch-prefixorauto-branch-prefix) that, when active, will modify the branch naming convention to include the type of Jira ticket. For instance:For bug tickets: Branches will be prefixed with "bugfix"
For story and task tickets: Branches will be prefixed with "feature"
For refactor tickets: Branches will be prefixed with "refactor"
This enhancement will improve branch naming consistency and aid in project organization.