Hi folks,
I'm out of ideas on what could be causing this problem.
Long story short, teams migrated from Bitbucket to Github.
Team was used to create release branches from Jira named like
release/1.49
In Bitbucket, branches like this could be created just fine from Jira. Now with Github, a strange error appears: "The issue key does not match the selected issue".
Interestingly enough, it does not seem to be a problem in github, as a branch can be created with this name there.
I don't recall seeing any validations set at Jira side specifically for the Github integration. Am I missing something?
Hello, the branch name should have the issuekey.
The format will be projectkey-issuenumber
like : SCRUM-1
Thanks - would you know by any chance if this is a Jira-side restriction in the Github integration?
The curious part is that when the team was using Bitbucket it seems this restriction never existed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, even with Bitbucket we need to use the issuekey for branch , commit .etc
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.