-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing branch name prefix #1886
Comments
Hi, thanks for using the Github-for-Jira app and reaching out to us! Just to make sure I understand it correctly: Do you mean if it's possible to change the Jira issue's type according to the branch name prefix entered during creating branches from Jira issue? If so, we don't currently support this functionality and it's not on our near term roadmap yet. I will keep a note of this in our future feature-requests. Thanks! |
Hi, I think you might have understood me correctly but just to make sure you do, I'll explain in more detail:
Is that an option or the string has to be the default which is defined in Jira? Thanks in advance! |
Thanks for clarifying it! At the moment we don't support this functionality yet, so it'd be a manual step to change the branch name for the time being. Cheers. |
Second this! |
Would be great, we use Git Workflow and need to name branches like this So a bit more flexibility when configuring the scheme would be nice! |
Echoing what others have said. We use Git Workflow and it would be helpful for the prefix to be added to the branch name when creating from Jira so that developers don't need to do this manually each time they create a branch. |
Agreed, this is something our team is used to and it would save us time if we could automate the prefixing of branch names. |
I agree. Vote +1 |
I agree as well. This is the way the Bitbucket integration works, btw. |
This would be ideal for me and my team! +1 vote! |
We also use git flow, so would be nice if this could be replicated when creating branches... |
We need this too! |
Any status here? Gitflow is probably the most popular workflow in Git, and it's surprising this wasn't supported right out of the box. We're using it, like many others, and it would help a lot if this is supported. |
Well we have found a simple solution: Likely migrating to Github Projects instead of JIRA. It held it's title long enough but the lack of support and the ever more cracking foundation of this monolith makes the newcomers shine a lot more. So many parts of JIRA get no love anymore since Atlassian seems to focus on cash milking their other cows nowadays... big company things. |
Is there anything going on in that direction? |
Hi,
I have integrated Jira with GitHub in order to create branches from Jira.
However, when I use issue_type as part of the branch name it can appear only as bug/ or task/. I would like it to be bugfix for Bugs and feature for Tasks / Story.
Is that at all possible?
The text was updated successfully, but these errors were encountered: