icon/x Created with Sketch.

Splunk Cookie Policy

We use our own and third-party cookies to provide you with a great online experience. We also use these cookies to improve our products and services, support our marketing campaigns, and advertise to you on our website and other websites. Some cookies may continue to collect information after you have left our website. Learn more (including how to update your settings) here.
Accept Cookie Policy

Accept License Agreements

This app is provided by a third party and your right to use the app is in accordance with the license provided by that third-party licensor. Splunk is not responsible for any third-party apps and does not provide any warranty or support. If you have any questions, complaints or claims with respect to this app, please contact the licensor directly.

Thank You

Downloading Atlassian JIRA Issue Alerts add-on for Splunk
SHA256 checksum (atlassian-jira-issue-alerts-add-on-for-splunk_110.tgz) e981116ea0667ce3cfad80500fa40ca19f735f278192b95adf6956be4da95c82 SHA256 checksum (atlassian-jira-issue-alerts-add-on-for-splunk_100.tgz) effd3c824419ba49f8df6e5e251bbbbf4334e0fc6b6205b3dc5de207ab549603
To install your download
For instructions specific to your download, click the Details tab after closing this window.

Flag As Inappropriate

Atlassian JIRA Issue Alerts add-on for Splunk

Admins: Please read about Splunk Enterprise 8.0 and the Python 2.7 end-of-life changes and impact on apps and upgradeshere.
This add-on helps to create customized Jira issues based on triggered events in Splunk.
It supports both Atlassian Jira Cloud and Atlassian Jira Server versions. Automatically detects which APIs need to use.
1. Cover all standart necessary fields in Atlassian Jira for issue creation such as Project, Summary, Issue Type, Priority, Description, Assignee, Labels, Components.
2. Add the result of Splunk Alert into the Jira issue at the end of the description field. There are two possible views of added data
1) The table view where table head consists of Splunk Alert result fields
2) The list view when the result of Splunk alert will be added as a Jira code snippet.
3. Possibility to use one additional custom field to create Jira issues.
4. Control what information from Splunk Alert will appear in Jira issues. Pass search result values dynamically into Jira issues.
Not necessary to use a digital ID of values in the Jira field. All fields take human-readable values.
Sample: you have a Jira project with a short name “CORP” with id=2331. In the configuration of Splunk Alert you don’t need to use the Id of Jira Project. You need to use the name of Project “CORP”. Atlassian JIRA Issue Alerts add-on will automatically convert human-readable values into digital Id.
5. Possibility to assign issues to specific people even if you don’t know UUID in Jira Cloud. Assignment by username.

System requirements

1.Splunk version 7.0 or greater
2.Windows, Linux or Mac OS operating system
3.Atlassian JIRA Cloud
4.Atlassian JIRA Server


App installation requires admin privileges.
Navigate to "Manage apps" and click "Install app from file".
Upload the app bundle.

Configuration Atlassian JIRA Issue Alerts add-on

In order to set up the app, navigate to "Manage apps" -> "Atlassian JIRA Issue Alerts". Click on "Launch app ".
On the setup screen you'll want to supply Proxy parameters and Add-on Settings parameters.
In the tab “Add-on Settings“ :
Add “Atlassian JIRA URL” with http:// or https:// at the start of url.
Add “JIRA username”. Use email of user account which you want to use for Jira issue creation.
Add “JIRA password” from Jira username above. For Jira Cloud you need to use “api user token”.
How to obtain “api user token” see https://confluence.atlassian.com/cloud/api-tokens-938839638.html
Your Jira users should have permission to create Jira issues, read Users and parameters of a project.

Configuration "JIRA Issue alert"



In order to investigate problems with the Slack alert action, you can check the logs of the
alert action.
Navigate to "Settings" -> "Alert actions"
Click on "View log events" for the Jira Issue Alert
* Or use Splunk search interface with SPL

index=_internal sourcetype=splunkd component=sendmodalert action="create_jira_issue"

You can also increase the verbosity of logs generated by the alert action by adjusting the
Navigate to "Settings" -> "Server settings" -> "Server logging"
Search for the log channel "sendmodalert"
Select logging level "DEBUG"

NOTE: This will increase cause detailed logs to be produced for all alert actions and might have an impact on system performance.

In order to get more information about every step of Jira issue alert add-on during issues creation and errors during the execution, you can check the logs of the Atlassian JIRA Issue Alerts add-on.
Navigate to the search interface of Splunk

index=_* sourcetype="taatlassianjiraissuealerts:log"

Note: For search in internal indexes in Splunk you need to have access to that.

Manually trigger the alert action

You can manually trigger the Jira issue alert action if you want to verify the configuration and/or preview different parameter combinations.
For example:
| sendalert =jira_issue_alert param.project="CORP" param.subject="Lorem ipsum" param.priority="P4" ....
Enter a similar SPL query into the search bar in the search interface of Splunk to manually send a message.

Error Codes

In case of an error when manually triggering the Jira issue alert action, you'll notice an error code being returned (eg. Alert script returned error code 6.)
Code 0 means Jira issue was successfully created.
Here are the possible error codes returned by the slack alert action:
Error Code 1: Jira issue creation failed
This error code indicates a problem with Jira issue creation. See logs for details.
Error Code 2: Validation Failed
This error code indications that the parameters handed to the alert action were invalid. Check the configuration.
Error Code 4: Build jira issue failed
This error code indicates a problem with Jira issue creation. See logs for details.
Error Code 5: Unexpected error
An unexpected error occurred while attempting to create the Jira issue.
See logs for details.

Release Notes

Version 1.1.0
June 14, 2020


- Improved Support for the python2.7.
- Improved processing of custom field name. Now you can type the text as you see in Jira. Sample: "Epic Link" instead of customfield_31.
- Improved view of attachment into a description of Jira ticket.

Issues fixes:
- TypeError: descriptor 'strip' requires a 'str' object but received a 'unicode'.

Version 1.0.0
May 24, 2020


Subscribe Share

AppInspect Tooling

Splunk AppInspect evaluates Splunk apps against a set of Splunk-defined criteria to assess the validity and security of an app package and components.

Are you a developer?

As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 10GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps and add-ons from Splunk, our partners and our community. Find an app or add-on for most any data source and user need, or simply create your own with help from our developer portal.

Follow Us:
© 2005-2020 Splunk Inc. All rights reserved.
Splunk®, Splunk>®, Listen to Your Data®, The Engine for Machine Data®, Hunk®, Splunk Cloud™, Splunk Light™, SPL™ and Splunk MINT™ are trademarks and registered trademarks of Splunk Inc. in the United States and other countries. All other brand names, product names, or trademarks belong to their respective owners.