---
title: Troubleshooting
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: Docs > Incident Response > Work Management > Troubleshooting
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# Troubleshooting

## Overview{% #overview %}

This guide is intended to help you resolve issues with third-party integrations in Work Management. If you continue to have trouble, reach out to [Datadog support](https://docs.datadoghq.com/help/) for further assistance.

## Jira{% #jira %}

Jira issue types with custom fields, private Jira projects, and on-premises Jira instances are not supported. If you are having trouble with automatic Jira ticket creation with syncing, see the following sections:

### Configuration{% #configuration %}

1. If Jira projects are not populating the dropdown on the Jira integration configuration screen, check that you have the `manage_integrations` permission.

1. Ensure that you have configured a webhook to receive events from Jira.

### Syncing and updates{% #syncing-and-updates %}

1. If you move a work item that is being synced with a Jira issue to a different Work Management project, the syncing stops. After it is moved, the work item in the new project does not have a Jira issue attached to it.
1. If you're updating the status of a work item in a way that is disallowed by a Jira workflow, the work item falls out of sync with the status mapping.
1. Updates to comments, including deletions, in either Work Management or Jira are not reflected on the other side.
1. Only work items created after the bidirectional integration was enabled are synced. Datadog does not retroactively sync work items that existed before the integration was enabled.

### Jira issue reporter{% #jira-issue-reporter %}

1. There are a few scenarios where the Jira issue reporter is reflected as the Datadog user that set up the Jira integration. Some of these scenarios include:
   - When a Datadog user that creates a work item does not have a Jira account
   - A Jira user has hidden email visibility
1. If the reporter on the mirrored Jira issue is updated, it is not reflected in Work Management, as the "created by" field is not editable.