You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Troubleshoot work item integration issues in Application Insights
9
9
10
-
[Work item integration](/azure/azure-monitor/app/work-item-integration) in Application Insights might not work as expected. This article offers general recommendations and specific troubleshooting steps.
10
+
[Work item integration](/azure/azure-monitor/app/work-item-integration) in Application Insights allows you to create and link work items directly from telemetry data. If this feature isn't working as expected, the following guidance will help you diagnose and resolve common issues.
11
11
12
12
## The "Create work item" option doesn't appear in transaction details
13
13
14
-
**Cause:** Work itemintegration isn't enabled or the resource isn't linked to Azure DevOps or GitHub.
14
+
If you don't see the option to create a work item, it usually means that integration hasn't been enabled or the resource isn't linked to Azure DevOps or GitHub.
15
15
16
-
**Check:** In Application Insights, go to **Work Items** and confirm that integration settings are configured.
16
+
**What to do:**
17
17
18
-
**Fix:** Enable integration and start from the **Create a work item** flow or use a workbook template.
18
+
* In Application Insights, navigate to **Work Items** and confirm that integration settings are configured.
19
+
* Start the process from the **Create a work item** flow or use a workbook template.
19
20
20
21
## On-premises Azure DevOps URL rejected
21
22
22
-
**Cause:** The URL format doesn't meet validation requirements.
23
+
This issue occurs when the URL format doesn't meet validation requirements.
23
24
24
-
**Check:** Ensure the URL uses HTTPS and matches the validation rule in the workbook parameter.
25
+
**What to do:**
25
26
26
-
**Fix:** Update the workbook's repository URL parameter and validation rule.
27
-
28
-
> [!NOTE]
29
-
> If using a self-hosted Azure DevOps instance, make sure it's accessible from the Azure portal.
27
+
* Make sure the URL uses HTTPS and matches the validation rule in the workbook parameter.
28
+
* If you're using a self-hosted Azure DevOps instance, ensure it is accessible from the Azure portal.
30
29
31
30
## Authorization prompt doesn't appear or linking fails
32
31
33
-
**Cause:** Popup blockers or cached tokens may prevent the prompt from appearing.
32
+
If you don't see the authorization prompt or linking fails, it may be caused by popup blockers or cached tokens.
34
33
35
-
**Check:** Disable popup blockers, allow third-party cookies, and clear your browser cache.
34
+
**What to do:**
36
35
37
-
**Fix:** Retry linking. If using OAuth, confirm that the required scopes are granted.
36
+
* Disable popup blockers and allow third-party cookies in your browser.
37
+
* Clear your browser cache and try linking again.
38
+
* If you're using OAuth, verify that the required scopes are granted.
38
39
39
40
## Work item creation fails with permission errors
40
41
41
-
**Cause:** Your account doesn't have sufficient permissions in Azure DevOps or GitHub.
42
-
43
-
**Check:** Verify account roles:
42
+
Permission errors typically mean your account doesn't have sufficient rights in Azure DevOps or GitHub.
44
43
45
-
* Azure DevOps: Needs *Contribute* permission.
46
-
* GitHub: Needs *Write* access.
44
+
**What to do:**
47
45
48
-
**Fix:** If using a Personal Access Token (PAT), ensure it includes **Work Items (read/write)** scope.
46
+
* For Azure DevOps, ensure you have *Contribute* permissions.
47
+
* For GitHub, confirm you have *Write* access to the repository.
48
+
* If you're using a Personal Access Token (PAT), make sure it includes *the Work Items (read/write)* scope.
49
49
50
50
## Template fails to load or save
51
51
52
-
**Cause:** Region limitations or missing permissions can prevent templates from loading or saving.
52
+
This problem often occurs due to region limitations or missing permissions.
53
53
54
-
**Check:** Confirm that the region supports the *Microsoft.Insights/workbooks* resource type and that the resource provider is registered in your subscription.
54
+
**What to do:**
55
55
56
-
**Fix:** Assign the *Microsoft.Insights/workbooks/write* role or try saving the template in a supported region.
56
+
* Verify that the region supports the *Microsoft.Insights/workbooks* resource type.
57
+
* Check that the resource provider is registered in your subscription.
58
+
* Assign the *Microsoft.Insights/workbooks/write* role or try saving the template in a supported region.
57
59
58
60
## Contextual data is missing from created work items
59
61
60
-
**Cause:** The Kusto Query Language (KQL) query doesn't return the expected schema.
62
+
If the work item doesn't include expected data, the Kusto Query Language (KQL) query may not return the correct schema.
61
63
62
-
**Check:** Run the query in **Logs** and validate the output fields.
64
+
**What to do:**
63
65
64
-
**Fix:** Update the query or bindings to match the expected schema.
66
+
* Run the query in **Logs** to confirm the output fields.
67
+
* Update the query or bindings to match the expected schema.
65
68
66
69
## Template isn't visible to other users
67
70
68
-
**Cause:** The template is saved as private or RBAC permissions are insufficient.
71
+
This usually happens when the template is saved as private or RBAC permissions are insufficient.
69
72
70
-
**Check:** Ensure the template is stored in a shared resource group and not saved as *My Reports*.
73
+
**What to do:**
71
74
72
-
**Fix:** Grant other users at least *Reader* access to the resource.
75
+
* Ensure the template is stored in a shared resource group and not saved as *My Reports*.
76
+
* Grant other users at least *Reader* access to the resource.
73
77
74
78
## Deleting a template doesn't remove existing links
75
79
76
-
**Cause:** Cached configuration persists after deletion.
80
+
Removing a workbook doesn't automatically clear cached configuration.
77
81
78
-
**Check:** Refresh the **Work Items** pane in Application Insights or clear your browser cache.
82
+
**What to do:**
79
83
80
-
**Fix:** If links persist, manually unlink them in the resource settings.
84
+
* Refresh the **Work Items** pane in Application Insights or clear your browser cache.
85
+
* If links persist, manually unlink them in the resource settings.
81
86
82
87
## GitHub issue or Azure DevOps item opens in the wrong repository or project
83
88
84
-
**Cause:** Incorrect default parameters or multiple templates override settings.
89
+
This happens when the default repository or organization URL is incorrect or multiple templates override settings.
85
90
86
-
**Check:** Open the workbook and confirm the default repository or organization URL parameter.
91
+
**What to do:**
87
92
88
-
**Fix:** Update defaults or remove conflicting templates.
93
+
* Open the workbook and confirm the default repository or organization URL parameter.
94
+
* Remove or update conflicting templates.
89
95
90
96
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
0 commit comments