-
Bug
-
Resolution: Not a bug
-
High
-
None
-
5.8.0, 5.10.1
-
None
-
1
-
Severity 1 - Critical
-
Issue
The JSM Mail Handler create duplicate tickets indefinitely from the same email when using MS Graph API as the protocol.
Environment
Replicable on any Jira Service Management (JSM) version that supports MS graph API (from 5.8.0).
Steps to replicate
- Configure an outgoing link with Azure following the instructions from this page, and using the scopes for the Microsoft Graph API protocol
- Configure a JSM Channel in a JSM project by following instructions from
this page
- Make sure to select the Outgoing Link as the authentication method, and MS Graph API as the protocol
Expected results
Only 1 JSM ticket per email should be created in the project.
Observed results
- relates to
-
JSDSERVER-12419 Microsoft Graph API integration for Incoming Mail handlers (JSM)
- Closed
[JSDSERVER-14003] The JSM Mail Handler create duplicate tickets indefinitely from the same email when using MS Graph API
Resolution | New: Not a bug [ 12 ] | |
Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
Support reference count | New: 1 |
Assignee | New: Mykhailo Kratiuk [ c76190bb6a9f ] |
Affects Version/s | New: 5.10.1 [ 105791 ] |
Link |
New:
This issue relates to |
Description |
Original:
h3. Issue
The JSM Mail Handler create duplicate tickets indefinitely from the same email when using MS Graph API as the protocol. h3. Replicable on any Jira Service Management (JSM) version that supports MS graph API (from 5.8.0). h3. Steps to replicate # Configure an outgoing link with Azure following the instructions from [this page|https://confluence.atlassian.com/jirakb/detailed-steps-to-configure-oauth-2-0-integration-with-microsoft-azure-1167706465.html], and using the scopes for the Microsoft Graph API protocol !Step_1.png|thumbnail! # Configure a JSM Channel in a JSM project by following instructions from [this page|https://confluence.atlassian.com/jiracore/set-up-an-email-channel-with-the-microsoft-graph-api-protocol-1224771936.html] !Step_2.png|thumbnail! #- Make sure to select the Outgoing Link as the authentication method, and MS Graph API as the protocol h3. Expected results Only 1 JSM ticket per email should be created in the project. h3. Observed results - JSM keeps creating indefinite tickets from the same email - The emails fetched by the JSM Mail Handler are not marked as READ |
New:
h3. Issue
The JSM Mail Handler create duplicate tickets indefinitely from the same email when using MS Graph API as the protocol. h3. Environment Replicable on any Jira Service Management (JSM) version that supports MS graph API (from 5.8.0). h3. Steps to replicate # Configure an outgoing link with Azure following the instructions from [this page|https://confluence.atlassian.com/jirakb/detailed-steps-to-configure-oauth-2-0-integration-with-microsoft-azure-1167706465.html], and using the scopes for the Microsoft Graph API protocol !Step_1.png|thumbnail! # Configure a JSM Channel in a JSM project by following instructions from [this page|https://confluence.atlassian.com/jiracore/set-up-an-email-channel-with-the-microsoft-graph-api-protocol-1224771936.html] !Step_2.png|thumbnail! #- Make sure to select the Outgoing Link as the authentication method, and MS Graph API as the protocol h3. Expected results Only 1 JSM ticket per email should be created in the project. h3. Observed results - JSM keeps creating indefinite tickets from the same email !Observed.png|thumbnail! - The emails fetched by the JSM Mail Handler are not marked as READ |
Description |
Original:
h3. Issue
The JSM Mail Handler create duplicate tickets indefinitely from the same email when using MS Graph API as the protocol. h3. Replicable on any Jira Service Management (JSM) version that supports MS graph API (from 5.8.0). h3. Steps to replicate # Configure an outgoing link with Azure following the instructions from [this page|https://confluence.atlassian.com/jirakb/detailed-steps-to-configure-oauth-2-0-integration-with-microsoft-azure-1167706465.html], and using the scopes for the Microsoft Graph API protocol !Step_1.png|thumbnail! # Configure a JSM Channel in a JSM project by following instructions from https://confluence.atlassian.com/jiracore/set-up-an-email-channel-with-the-microsoft-graph-api-protocol-1224771936.html #- Make sure to select the Outgoing Link as the authentication method, and MS Graph API as the protocol h3. Expected results Only 1 JSM ticket per email should be created in the project. h3. Observed results - JSM keeps creating indefinite tickets from the same email - The emails fetched by the JSM Mail Handler are not marked as READ |
New:
h3. Issue
The JSM Mail Handler create duplicate tickets indefinitely from the same email when using MS Graph API as the protocol. h3. Replicable on any Jira Service Management (JSM) version that supports MS graph API (from 5.8.0). h3. Steps to replicate # Configure an outgoing link with Azure following the instructions from [this page|https://confluence.atlassian.com/jirakb/detailed-steps-to-configure-oauth-2-0-integration-with-microsoft-azure-1167706465.html], and using the scopes for the Microsoft Graph API protocol !Step_1.png|thumbnail! # Configure a JSM Channel in a JSM project by following instructions from [this page|https://confluence.atlassian.com/jiracore/set-up-an-email-channel-with-the-microsoft-graph-api-protocol-1224771936.html] !Step_2.png|thumbnail! #- Make sure to select the Outgoing Link as the authentication method, and MS Graph API as the protocol h3. Expected results Only 1 JSM ticket per email should be created in the project. h3. Observed results - JSM keeps creating indefinite tickets from the same email - The emails fetched by the JSM Mail Handler are not marked as READ |
Description |
Original:
h3. Issue
The JSM Mail Handler create duplicate tickets indefinitely from the same email when using MS Graph API as the protocol. h3. Replicable on any Jira Service Management (JSM) version that supports MS graph API (from 5.8.0). h3. Steps to replicate # Configure an outgoing link with Azure following the instructions from https://confluence.atlassian.com/jirakb/detailed-steps-to-configure-oauth-2-0-integration-with-microsoft-azure-1167706465.html, and using the scopes for the Microsoft Graph API protocol # Configure a JSM Channel in a JSM project by following instructions from https://confluence.atlassian.com/jiracore/set-up-an-email-channel-with-the-microsoft-graph-api-protocol-1224771936.html #- Make sure to select the Outgoing Link as the authentication method, and MS Graph API as the protocol h3. Expected results Only 1 JSM ticket per email should be created in the project. h3. Observed results - JSM keeps creating indefinite tickets from the same email - The emails fetched by the JSM Mail Handler are not marked as READ |
New:
h3. Issue
The JSM Mail Handler create duplicate tickets indefinitely from the same email when using MS Graph API as the protocol. h3. Replicable on any Jira Service Management (JSM) version that supports MS graph API (from 5.8.0). h3. Steps to replicate # Configure an outgoing link with Azure following the instructions from [this page|https://confluence.atlassian.com/jirakb/detailed-steps-to-configure-oauth-2-0-integration-with-microsoft-azure-1167706465.html], and using the scopes for the Microsoft Graph API protocol !Step_1.png|thumbnail! # Configure a JSM Channel in a JSM project by following instructions from https://confluence.atlassian.com/jiracore/set-up-an-email-channel-with-the-microsoft-graph-api-protocol-1224771936.html #- Make sure to select the Outgoing Link as the authentication method, and MS Graph API as the protocol h3. Expected results Only 1 JSM ticket per email should be created in the project. h3. Observed results - JSM keeps creating indefinite tickets from the same email - The emails fetched by the JSM Mail Handler are not marked as READ |
Attachment | New: Step_2.png [ 442501 ] | |
Attachment | New: Step_1.png [ 442500 ] | |
Attachment | New: Observed.png [ 442499 ] |
Closing this bug as invalid, since the issue is caused by incorrect API permissions and App Link scopes configuration coming from the documentation https://confluence.atlassian.com/jirakb/detailed-steps-to-configure-oauth-2-0-integration-with-microsoft-azure-1167706465.html.
I raised a separate bug to fix our documentation:
https://jira.atlassian.com/browse/JSDSERVER-14011