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 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 errors listed below:

  • 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.

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

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.