guilhemmarchand
commented
2 years ago Hi @Gm0ur4
Please enable DEBUG logging:
The Add-on will now log the entire JSON data sent to the JIRA API:
(index="_internal" OR index="cim_modactions") (source="*jira_service_desk_modalert.log") "json data for final rest call"
Ex:
2022-01-06 20:54:10,520 DEBUG pid=2528870 tid=MainThread file=cim_actions.py:message:292 | sendmodaction - signature="json data for final rest call:={
"fields": {
"project": {
"key": "LAB"
},
"summary": "test JIRA from Splunk Cloud",
"description": "Test JIRA alert",
"issuetype": {
"name": "Bug"
},
"priority": {
"name": "Medium"
}
}
}" action_name="jira_service_desk" sid="1641502448.163365" rid="0" app="TA-jira-service-desk-simple-addon" user="guilhem.marchand@gmail.com" action_mode="adhoc"This is to make sure all fields are populated and consistents.
The error:
{"summary":"Field 'summary' cannot be set.
"description":"Field 'description' cannot be set. It is not on the appropriate screen, or unknown."}}Is returned by JIRA, it normally indicated a configuration issue on the JIRA project side, with the knowledge of the logging you will know more, but it's very likely an issue of your own.
Gm0ur4
Hi! We use the app to integrate Splunk with our Jira account. It has happened that some calls coming from splunk do not automatically open in jira (the same alert opens at certain times, then it stops opening).
The error I get is the following:
HTTP Error=400, content={"errorMessages":[],"errors":{"summary":"Field 'summary' cannot be set. "description":"Field 'description' cannot be set. It is not on the appropriate screen, or unknown."}}" action_name="jira_service_desk_replay" search_name="JIRA Service Desk - Resilient store Tracker"
The login used in the integration has admin access in jira and within the project.