All Apps and Add-ons

Jira Service Desk simple AddOn sometimes sends null values(Customfields)

Newbie_geonu
New Member

Hello experts. I'm a Splunk newbie.

I am using the Jira Service Desk simple AddOn to send Splunk alarms to Jira tickets.

We also confirmed that Splunk alarms were successfully raised through Jira tickets. However, sometimes it is the same alarm, but a specific alarm receives the customfield value well, but there are cases where no value is retrieved.

 

In Splunk, it is confirmed that the value exists, but the value cannot be retrieved. No matter how much I searched, I couldn't find out what the reason was. If the Jira and Splunk field mappings are incorrect, you shouldn't be able to get the value from all tickets, but you can't get it from a specific ticket... What's the problem?

Example here... The Client value is always a value. However, as shown in the images, the customer value does not exist. 

Newbie_geonu_2-1731567740023.png

[Error Ticket]

 

Newbie_geonu_3-1731567815400.png

[Normal Ticket]

 

 

 

 

Labels (2)
0 Karma
Get Updates on the Splunk Community!

Cloud Platform & Enterprise: Classic Dashboard Export Feature Deprecation

As of Splunk Cloud Platform 9.3.2408 and Splunk Enterprise 9.4, classic dashboard export features are now ...

Explore the Latest Educational Offerings from Splunk (November Releases)

At Splunk Education, we are committed to providing a robust learning experience for all users, regardless of ...

New This Month in Splunk Observability Cloud - Metrics Usage Analytics, Enhanced K8s ...

The latest enhancements across the Splunk Observability portfolio deliver greater flexibility, better data and ...