Jira Issue keys in pull request title and commits omits trailing digits if there are multiple Jira issue keys in a title/commit and the keys are written keys in a specific pattern

Summary

It looks like the link to Jira issues omit trailing digits if there are multiple Jira issue keys in a title/commit - and if the title/message contains issues keys in the following pattern for example:

KEY-1, KEY-1X, KEY-1XXX

For example, an issue key number, KEY-1 is set first, and then, if the next Jira key set on the same sentence has 'KEY-1' on the issue key as well, for example, KEY-102, the 'KEY-1' will be highlighted while the '02' will be left out for some reason.

How to Replicate

1. Connect Bitbucket to a Jira instance via applinks
2. Perform some new commits into a repo and create a pull request with the following title

   PRO-1, PRO-123, PRO-1254

Expected Results

All Jira keys in the pull request title should be parsed correctly and link to their respective issues on Jira

Actual Results

Digits get omitted from the Jira issue keys, for example:

Looks to occur on commit messages as well

Workaround

Rename the pull request titles and move around the order of the Jira issue keys in the title