problems with issue-key rendering if custom project key pattern set

we set the jira.projectkey.pattern property to a pattern like

((\d{5})|([A-Z][A-Z0-9]+))

(yes, we didn't followed the "starting with a letter" rule, but in 4.4.5 this rule was not obvious for us).

After that ( we didn't noticed the relationship) we noticed, that rendring of issue keys (like RPL-234) in description and comments was not as a link, but as RPLnullRPL-234 ... ugly.

After investigating, I think the problem is in JiraKeyUtils.java, especially createKeyFromMatchingGroups seems to ignore the circumstance, that there can be more than 1 alternative for the project key. My workaround (see the patch file) is to change the issueKeyRegex patterns of the DefaultKeyMatcher and to change the way, the key is combined in createKeyFromMatchingGroups. For us (I think) it's working like intended now ... maybe you can use it