Hey Sten,

I don't recall the issue prior to the upgrade, I think we came up from 2.5.2 . The only thing I can guarantee is that with my users someone would have noticed.

Cheers,
Steven.

Sten also see my original issue here https://support.atlassian.com/browse/FSH-9215

This was on fecru 2.7.10

Hey Steven,

Thanks for the screenshots, I understand better what you are referring to now. Could you tell me if, prior to your upgrade, the issues for the projects with underscores were properly displayed?

Thanks

Hey Again, Doesn't seem like I have access to upload files. The screen shot is in the issue I filed. https://support.atlassian.com/browse/CRC-3978

Hey Sten,

I'm not sure that this was explained well. The only issue seems to be that the jira activity stream is not displaying the issue key, it is in fact retrieving the issue properly. The keys are working properly everywhere else. I've attached a screen shot, when you see it I believe the issue will make more sense.

Thanks,
Steven.

Hi Tom,

Unfortunately we are not supporting customized JIRA issue keys. You will be able to add your own linker (cf https://confluence.atlassian.com/display/FISHEYE/Linkers)

Cheers

It appears in my limited testing that this holds true for any project key with one or more Numeric Digits in.
Custom patterns with alpha characters are handled as expected.
I have not tested any special characters