Has anyone tried a forward slash in branch names, e.g., "dev/my-branch"?

[Oleg Merlugov]

Does anyone know if Jira-GitHub integration has any problems with a forward slash in GitHub branch names?

GitHub explicitly allows forward slash '/' in branch names, so that branches can be neatly grouped by their type, e.g., "dev/JRA-123", "bug/JRA-234".

Jira appears to work with such branches too! For example, on the ".../browse/JRA-123" page, under Development details, I can see the linked branch "dev/JRA-123" from GitHub. 

Unlike GitHub, however, Jira documentation does not mention forward slashes. It just says that the branch name needs to include the issue key for the integration to work. So, given that my IDE and CI tools fully support this, I was wondering about any potential issues in Jira with this naming convention.

Here is a relevant excerpt from Jira documentation: https://support.atlassian.com/jira-software-cloud/docs/reference-issues-in-your-development-work/ :

---

Branches

Include the issue key in the branch name when you create the branch to link it to your Jira issue.

For example: git checkout -b JRA-123-<branch-name>

This works by default in connected Bitbucket, GitLab, GitHub, GitHub Enterprise, and Fisheye tools.

If you’re using Bitbucket Cloud, GitHub or GitLab, you can create a branch directly from your Jira issue. Under Development, select Create branch. If you create a branch this way, the issue key is automatically added to the name of the branch.

---

Thank you!