Bug still affects our cloud instance as well

This bug still happens to me

Thanks @mjopson ,

My original request to BB is raising that exact issue - fixing the latest bug that you raised will resolve our issue.

Thanks.

@oasissystems - thanks for commenting on this issue.
I've created a new issue to track the required fix at BCLOUD-16614

I will close this issue once more as it is for a different change, that Jira issue keys not be case-sensitive for linking, which will not be fixed.
For further details and commentary please view BCLOUD-16614

Kind regards,
Martin

Bitbucket,
Product Manager

Hi Kaleb @belak + all. This bug needs to be re-opened. I am using Bitbucket Cloud and Jira Cloud - you cannot create a project in Jira with a lowercase key.

We require this fix for Bitbucket.

https://confluence.atlassian.com/jiracorecloud/editing-a-project-s-details-938021482.html

#!na
2. In the Key field, enter your desired key. Your project's key must be at least 2 characters long and contain only uppercase letters.

I followed up with the JIRA team a while ago and it sounds like this is by design. JIRA project keys can be case sensitive, so this just follows that decision.

This is a bug in the DVCS connector. I'll make sure it gets to the right team.

For now, you can work around it by manually setting up your Jira connections using the Jira link type, rather than the custom one which is set up by the DVCS connector.

You can view the issue on this branch url: https://bitbucket.org/nexonia/assistant/commits/branch/bug-ip-199

If you have access. I have one commit with ip-199 that is not linked, and one with IP-199 that is linked.

Can you provide more information about this? I wasn't able to reproduce it when I set up the jira link myself.

This is indeed annoying and not very smart.