Ability to configure naming convention when creating branch from issue

Comments: 18

Oldest • Newest • Most likes • Fewest likes

• Add a comment
• 12 Oct, '22
  KB

  Highlighted comment
  
  I agree 100%

  Copy link to this comment
• 25 Jan, '22
  Freddy Henin

  +1, this would be super helpful

  Copy link to this comment
• 22 Mar, '22
  Aleksa Jonic

  This would be amazing.

  Copy link to this comment
• 30 Apr, '22
  Diego Perez

  This would be really helpful.

  Copy link to this comment
• 26 May, '22
  Aelx W

  I just complained about this and was directed to this suggestion. I don't know why the feature was changed to automatically name the branch....

  Copy link to this comment
• 29 May, '22
  Jon Karnofsky

  +1, would like this also.

  Copy link to this comment
• 08 Jun, '22
  Antoine

  That'd be really neat, I hope we can have it in a near future.

  Copy link to this comment
• 05 Jul, '22
  GrumpyDev74

  I agree. That feature is a SHOULD HAVE !

  Copy link to this comment
• 15 Jul, '22
  Neil Simmons

  I agree. The current default name conflicts with the gitflow and branch foldering features.

  Copy link to this comment
• 06 Oct, '22
  Imre

  100% agree, this feature would be very useful for our team!

  Copy link to this comment
• 09 Nov, '22
  Martin

  Yes, please.

  Copy link to this comment
• 07 Dec, '22
  Pedro

  This would be specially helpful for GitHub integrations (such as ClickUp) that track for exact strings (case sensitive and/or with special characters)

  Copy link to this comment
• 20 Mar, '23
  Yon

  Yes. Can we please have this - it would be so helpful.

  Copy link to this comment
• 09 May, '23
  Adam Ladanyi

  Been asking for this for AGES.

  Copy link to this comment
• 18 May, '23
  Chad

  This would be a HUGE help instead of relying on our users to manually modify the generated branch name to fit the convention that our company has established. We actually preface all of our "Work Item" branches with "wi/" (Ex. wi/1234_PascalCaseOfShortenedWorkItemDescription) so they show in a subfolder as a group that can be collapsed, and prioritize our top-level branches which are used for deployments to multiple environments.

  1 Copy link to this comment
• 19 Jan, '24
  Joey Kelroy System

  "Branch name templates" (suggested by <Hidden> on 2024-01-18), including upvotes (1) and comments (0), was merged into this suggestion.

  Copy link to this comment
• 16 Apr, '24
  Mike Tafel

  It'd be great if the template could specify that you want the branch could be prefixed with a the jira ticket type i.e. bug/<branch-name> or story/<branch-name> or task/<branch-name>

  1 Copy link to this comment
• 18 Oct, '24
  Bas

  Oh yes please!

  Copy link to this comment