Summary

JIRA Smart Commit Error when Issue Key Doesn't Exist on Instance

Steps to Reproduce

1. Connect JIRA and Bitbucket together with application link and enable smart commits
2. Ensure you have a username and email that matches on both instances.
3. Enable outbound email on JIRA
4. Create a git commit that references an issue key that doesn't exist on the JIRA instance and and uses some additional action such as #comment or #time

Expected Results

• JIRA will ignore the smart commit in cases where the issue key doesn't exist

Actual Results

• When connected to a single external provider, JIRA will attempt to match the smart commit to that one and send a failure email if the issue key doesn't exist.
• When connected to multiple external providers (e.g., GitHub and Bitbucket), JIRA will successfully process the smart commit on the matching provider. However, for the other provider(s), if the issue key doesn't exist, it will still send a failure email with the following message:

There was an error processing your smart commit
Commit Icon
450bb68
Tuesday, February 20, 2018 3:00:12 PM CET
Due to the following errors we could not process your smart commit. You need to perform the action on the issue manually.
1 command created an error

Notes

For environments where multiple JIRA instances are connected to Bitbucket with the same user bases this will result in unnecessary failure emails. These confuse users and drive support calls.

Workaround

none at this time, except for client-side email filtering.