-
Bug
-
Resolution: Fixed
-
Low (View bug fix roadmap)
-
7.2.13, 7.3.7, 7.6.4
-
7.02
-
12
-
Severity 3 - Minor
-
2
-
Summary
JIRA Smart Commit Error when Issue Key Doesn't Exist on Instance
Steps to Reproduce
- Connect JIRA and Bitbucket together with application link and enable smart commits
- Ensure you have a username and email that matches on both instances.
- Enable outbound email on JIRA
- 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.
Update September 2024
We have a solution for this issue coming soon in 10.2.0.
We were unable to change the existing behaviour by default, as some users may be depending on being notified of incorrect project keys. However, we have added an opt-out to allow disabling of this notification for those that use multiple Jira instances.
To do this, you will need to execute a PUT command to the rest API like so:
https://{yourjiraurl}/rest/smart-commits/1.0/config/notification?notificationKey=smart-commit-notify-unknown-issue&enabled=false
Note this will have to be performed on each Jira instance connected to your GIT provider via DVCS.
[JSWSERVER-16450] JIRA Smart Commit Error when Issue Key Doesn't Exist on Instance
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
| Remote Link | Original: This issue links to "Page (Confluence)" [ 953490 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 953490 ] |
| Description |
Original:
h3. Summary
JIRA Smart Commit Error when Issue Key Doesn't Exist on Instance h3. Steps to Reproduce # Connect JIRA and Bitbucket together with application link and enable smart commits # Ensure you have a username and email that matches on both instances. # Enable outbound email on JIRA # 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}} h3. Expected Results - JIRA will ignore the smart commit in cases where the issue key doesn't exist h3. 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: {quote}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 {quote} !smart_commit.png|thumbnail! h3. 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. h3. Workaround none at this time, except for client-side email filtering. |
New:
h3. Summary
JIRA Smart Commit Error when Issue Key Doesn't Exist on Instance h3. Steps to Reproduce # Connect JIRA and Bitbucket together with application link and enable smart commits # Ensure you have a username and email that matches on both instances. # Enable outbound email on JIRA # 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}} h3. Expected Results - JIRA will ignore the smart commit in cases where the issue key doesn't exist h3. 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: {quote}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 {quote} !smart_commit.png|thumbnail! h3. 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. h3. Workaround none at this time, except for client-side email filtering. {panel:title=Update September 2024|titleBGColor=#d3d3d3|bgColor=#d3d3d3} We have a solution for this issue coming soon in 10.2.0. We were unable to change the existing behaviour by default, as some users may be depending on being notified of incorrect project keys. However, we have added an opt-out to allow disabling of this notification for those that use multiple Jira instances. To do this, you will need to execute a PUT command to the rest API like so: {code}https://{yourjiraurl}/rest/smart-commits/1.0/config/notification?notificationKey=smart-commit-notify-unknown-issue&enabled=false{code} Note this will have to be performed on each Jira instance connected to your GIT provider via DVCS. {panel} |
| Fix Version/s | New: 10.2.0 [ 108819 ] |
| Status | Original: In Progress [ 3 ] | New: Waiting for Release [ 12075 ] |
| Status | Original: Gathering Impact [ 12072 ] | New: In Progress [ 3 ] |
| Assignee | New: Benjamin Suess [ c8bcca445054 ] |
| Description |
Original:
h3. Summary
JIRA Smart Commit Error when Issue Key Doesn't Exist on Instance h3. Steps to Reproduce # Connect JIRA and Bitbucket together with application link and enable smart commits # Ensure you have a username and email that matches on both instances. # Enable outbound email on JIRA # 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}} h3. Expected Results - JIRA will ignore the smart commit in cases where the issue key doesn't exist h3. Actual Results JIRA will send an email to the user performing the commit with the following messaging: {quote} 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 {quote} !smart_commit.png|thumbnail! h3. 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. h3. Workaround none at this time, except for client-side email filtering. |
New:
h3. Summary
JIRA Smart Commit Error when Issue Key Doesn't Exist on Instance h3. Steps to Reproduce # Connect JIRA and Bitbucket together with application link and enable smart commits # Ensure you have a username and email that matches on both instances. # Enable outbound email on JIRA # 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}} h3. Expected Results - JIRA will ignore the smart commit in cases where the issue key doesn't exist h3. 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: {quote}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 {quote} !smart_commit.png|thumbnail! h3. 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. h3. Workaround none at this time, except for client-side email filtering. |
| UIS | Original: 4 | New: 2 |