Describe the bug
When committing, the Jira issue key must be the same Capitalization. I don't know if Jira keys are case sensitive (this issue is assuming that they aren't), but it would be nice if when looking through commits it could case-insensitive.
In Jira, if you try to navigate to issue key abc123 it will redirect you to ABC123 so I assume it is not case sensitive.
To Reproduce
Create a commit with a Jira key such as abc123 in the commit message.
Release it in a pipeline.
Observe it does not appear in the Work Items section of the AzureDevops pipeline.
Expected behavior
Either an option to make it case insensitive, or at least a mention in the documentation that it is indeed case sensitive.
Screenshots
There is a commit "brmi-361" that does not pick up the Jira issue.
Desktop (please complete the following information):
Browser Chrome
Version AzureDevops Git Repo + AzureDevops Pipeline + Jira
Describe the bug When committing, the Jira issue key must be the same Capitalization. I don't know if Jira keys are case sensitive (this issue is assuming that they aren't), but it would be nice if when looking through commits it could case-insensitive.
In Jira, if you try to navigate to issue key abc123 it will redirect you to ABC123 so I assume it is not case sensitive.
To Reproduce
Expected behavior Either an option to make it case insensitive, or at least a mention in the documentation that it is indeed case sensitive.
Screenshots There is a commit "brmi-361" that does not pick up the Jira issue.
Desktop (please complete the following information):