Skip to content

Troubleshoot the Splunk Add-on for Jira Cloud

For troubleshooting tips that apply to all add-ons, see Troubleshoot add-ons in Splunk Add-ons. For additional resources, see Support and resource links for add-ons in Splunk Add-ons.

Ensure that the required permissions are provided to the account that configures the API Token for fetching Jira Issues using modular input, creating a Jira issue, or update an existing Jira issue using Alert Action.

If appropriate permissions are not provided, you might encounter one of the following errors:

  • Field ‘summary’ cannot be set. It is not on the appropriate screen, or unknown.
  • Field ‘components’ cannot be set. It is not on the appropriate screen, or unknown.
  • Field ‘customfield’ cannot be set. It is not on the appropriate screen, or unknown.
  • Field ‘description’ cannot be set. It is not on the appropriate screen, or unknown.
  • Field ‘priority’ cannot be set. It is not on the appropriate screen, or unknown.
  • Field ‘labels’ cannot be set. It is not on the appropriate screen, or unknown.
  • You do not have permission to create issues in this project.
  • Issue does not exist or you do not have permission to see it.
  • Can’t move (TEMP-123). You might not have permission, or the issue is missing required information. If you keep having this problem, contact your Jira Administrator.

See the Hardware and Software Requirement section of the Splunk documentation of this add-on.

Troubleshoot custom fields in alert actions and custom commands

Search the dedicated alert-action log before troubleshooting a failed Jira issue creation or update:

index=_internal source="*/splunk_ta_jira_cloud_alert_action_*"
| sort 0 _time
| table _time host source log_level _raw

Use the following guidance for custom-field errors:

Error or symptom Cause and resolution
Invalid cascading-select value for custom field '<field name>'. Use Parent or Parent::Child. Enter either a non-empty parent option or a non-empty parent and child separated by one :: delimiter. Do not use :: within an option name.
Custom fields not found in Jira: <field name>. Use the exact, case-sensitive Jira field display name. Do not use an internal ID such as customfield_10258.
Jira rejects a cascading-select option Confirm that the parent and child option names match Jira exactly and that the child belongs to the selected parent. Jira validates option availability for the selected project and issue type.
Jira reports that a custom field cannot be set or is unknown Confirm that the field is present on the appropriate Jira create or edit screen and that the configured account has permission to perform the operation.

For the complete custom-field syntax, see Configure custom fields.

Known Case: Minimal Data Duplication in Jira Cloud Users Modular Input

The JIRA Users APIs expose only limited user data and do not include any time-related fields in their response. As a result, the index will have minimal data duplication, when user information is updated/deleted or new users are added in JIRA Cloud.