Support lower case issue keys

There have been a number of user reports around lower case issue keys.

Reviews on Atlassian Marketplace (link)

Issues

When using the DVCS Connector a branch name feature/lief-12155-test-jira was being correctly linked to the ticket LIEF-12155 in JIRA. This doesn’t work anymore with the new GitHub for Jira app. I have to use feature/LIEF-12155-test-jira (please note the capitalised project name).

– https://github.com/integrations/jira/issues/188

What does DVCS support?

Officially, Smart Commits doesn’t support lower case issue keys:

Smart Commits only support the default Jira Software issue key format. This format is two or more uppercase letters, followed by a hyphen and the issue number, for example JRA-123. – Atlassian Smart Commits

However, I have reproduced one case where lower case issue keys are extracted using DVCS:

1. Create a ticket, JRA-1.
2. Create a branch, jra-1-something-good
3. Push branch to GitHub

In JIRA with DVSC Connector turned on, jra-1-something-good will appear in the Development side bar on JRA-1. When the branch starts with something else—feature/jra-1-something-good—the branch is not extracted.

It appears that DVCS Connector supports some lower case issue keys but, generally, doesn’t. Still some work to be done to suss out exactly what is supported by DVCS.

[conf]

This. Please, add support for lower-case issue keys, it’s just more tiring to type a branch name like JRA-123-do-something-important instead of jra-123-do-something-important (and also such a branch name feels weird).

[rachellerathbone]

Hi @jnraine. I’m from a team at Atlassian that is currently in the process of migrating the ownership over to us from GitHub. As a part of this, we’re currently going through the backlog of issues and prs to see what can still be addressed and what should be closed.

Adding broader support for issue keys is something we’re actively discussing and have tickets in our backlog. Stay tuned 😄