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
14
14
15
-
[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 helps you diagnose and resolve common issues.
15
+
[Work item integration](/azure/azure-monitor/app/work-item-integration) in Application Insights enables you to create and link work items directly from telemetry data. If this feature isn't working as expected, the following guidance helps you to diagnose and resolve common issues.
16
16
17
17
## The "Create work item" option doesn't appear in transaction details
18
18
19
-
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.
19
+
If you don't see the option to create a work item, it's likely that integration wasn't enabled or the resource isn't linked to Azure DevOps or GitHub.
20
20
21
21
**What to do:**
22
22
23
-
1. In Application Insights, navigate to **Work Items** and confirm that integration settings are configured.
24
-
1. Start the process from the **Create a work item** flow or use a workbook template.
23
+
1. In Application Insights, navigate to **Work Items**, and verify that integration settings are configured.
24
+
1. Start the process from the **Create a work item** flow, or use a workbook template.
25
25
26
26
## On-premises Azure DevOps URL rejected
27
27
28
-
This issue occurs when the URL format doesn't meet validation requirements.
28
+
This issue occurs if the URL format doesn't meet validation requirements.
29
29
30
30
**What to do:**
31
31
32
-
* Make sure the URL uses HTTPS and matches the validation rule in the workbook parameter.
33
-
* If you're using a self-hosted Azure DevOps instance, ensure it's accessible from the Azure portal.
32
+
* Make sure that the URL uses the HTTPS protocol and matches the validation rule in the workbook parameter.
33
+
* If you're using a self-hosted Azure DevOps instance, make sure that it's accessible from the Azure portal.
34
34
35
35
## Authorization prompt doesn't appear or linking fails
36
36
37
-
If you don't see the authorization prompt or linking fails, it can be caused by popup blockers or cached tokens.
37
+
If you don't see the authorization prompt, or if linking fails, the cause might be a pop-up blocker or cached tokens.
38
38
39
39
**What to do:**
40
40
41
-
* Disable popup blockers and allow third-party cookies in your browser.
42
-
* Clear your browser cache and try linking again.
41
+
* Disable pop-up blockers and allow third-party cookies in your browser.
42
+
* Clear your browser cache, and then try again to link.
43
43
* If you're using OAuth, verify that the required scopes are granted.
44
44
45
-
## Work item creation fails with permission errors
45
+
## Work item creation fails and returns permission errors
46
46
47
-
Permission errors usually mean your account doesn't have sufficient rights in Azure DevOps or GitHub.
47
+
Permission errors usually indicate that your account doesn't have sufficient rights in Azure DevOps or GitHub.
48
48
49
49
**What to do:**
50
50
51
51
* For Azure DevOps, ensure you have *Contribute* permissions.
52
52
* For GitHub, confirm you have *Write* access to the repository.
53
-
* If you're using a Personal Access Token (PAT), make sure it includes the *Work Items (read/write)* scope.
53
+
* If you're using a Personal Access Token (PAT), make sure it includes *the Work Items (read/write)* scope.
54
54
55
-
## Template fails to load or save
55
+
## Template doesn't load or save
56
56
57
-
This problem often occurs due to region limitations or missing permissions.
57
+
This issue typically occurs because of region limitations or missing permissions.
58
58
59
59
**What to do:**
60
60
61
61
* Verify that the region supports the *Microsoft.Insights/workbooks* resource type.
62
62
* Check that the resource provider is registered in your subscription.
63
-
* Assign the *Microsoft.Insights/workbooks/write* role or try saving the template in a supported region.
63
+
* Assign the *Microsoft.Insights/workbooks/write* role, or try saving the template in a supported region.
64
64
65
65
## Contextual data is missing from created work items
66
66
67
67
If the work item doesn't include expected data, the Kusto Query Language (KQL) query might not return the correct schema.
68
68
69
69
**What to do:**
70
70
71
-
* Run the query in **Logs** to confirm the output fields.
71
+
* Run the query in **Logs** to verify the output fields.
72
72
* Update the query or bindings to match the expected schema.
73
73
74
74
## Template isn't visible to other users
75
75
76
-
This usually happens when the template is saved as private or role-based access control (RBAC) permissions are insufficient.
76
+
This issue usually occurs if the template is saved as private, or if role-based access control (RBAC) permissions are insufficient.
77
77
78
78
**What to do:**
79
79
80
-
*Ensure the template is stored in a shared resource group and not saved as *My Reports*.
80
+
*Make sure that the template is stored in a shared resource group and not saved as *My Reports*.
81
81
* Grant other users at least *Reader* access to the resource.
82
82
83
83
## Deleting a template doesn't remove existing links
0 commit comments