I’m trying to connect DataDog alerts with Jira ticket creation. Our setup already works fine for creating basic tickets when monitors trigger alerts, but I need to link these tickets to an existing Epic in Jira.
From the Jira API documentation, I can see that Epics use this field structure:
"customfield_10002": "TEAM-1234"
I’m not sure how to properly format this in the DataDog integration settings. I’ve attempted various approaches to include this custom field data but haven’t found the right configuration yet.
The current integration creates standalone tickets without any issues, but I need them grouped under a specific Epic. Has anyone successfully configured this type of Epic association in DataDog’s Jira integration?
i had a similar issue before. make sure to include the epic link in the json payload under the datadog settings. just add "customfield_10002": "YOUR-EPIC-KEY" in the extra fields section. it worked for me after some trial and error.
Epic linking through DataDog is a pain - the field mapping never works like you’d expect. Here’s what finally worked for me: skip the JSON tweaking and go straight to the DataDog Jira integration config. Add the Epic field under “Issue Creation” and map it as a custom field using your exact field ID (customfield_10002). When you set the Epic key value, don’t use quotes in DataDog’s interface - I know their API docs show quotes, but the interface wants it without them. Also check that your DataDog service account actually has Epic linking permissions in your Jira project. That one got me stuck for way too long.
Epic field mapping is a pain - DataDog often screws up custom field formats during API calls. I ditched the built-in Jira integration and went with DataDog webhooks instead. Set up a custom webhook that sends alert data to a middleware service, which then formats the Jira API request properly with Epic association. Way better control over field mapping and killed all the formatting issues I had. Takes more setup upfront, but it fixed the Epic linking and gave me flexibility for other custom fields we needed. If you’re stuck with the direct integration, make sure you’ve got the latest Jira integration version - older ones had nasty bugs with custom field handling.