| jira MODE OPTIONS
| jira filters
| jira issues FILTER_ID
| jira jqlsearch "JQL_QUERY"
| jira changelog "JQL_QUERY"
| jira rapidboards list|all|(RAPIDBOARD_ID [detail sprints|issues])
RAPIDBOARD_ID will list all sprints in one specific scrum board.
Pipe search results into a jqlsearch
| search ... | eval foo="WTF-1,WTF-2,WTF-3" | makemv delim=, foo | map search="|jira batch JQL_QUERY $foo$"
Compatible with issues, jqlquery, and batch commands.
changefield
Compatible with issues, jqlquery and batch commands.
changetime TIME_FIELD
Compatible with issues, jqlquery, and batch commands.
fields "[INTERNAL_FIELD_NAME,...]"
From version 2.2.0, you can index JIRA ticket with jira modular input.
Once the modular input is enabled, it will start sync process which based on jql query to fetches tickets from JIRA server. After sync process finishes, the modular input will get updated tickets every "interval" seconds.
This is one example of inputs.conf, for using it, configure your server and credential then copy to local/inputs.conf.
[jira://buttercup]
sourcetype = jira
index=jira
interval = 60
server = jira.buttercup.com
protocol = https
port = 443
jql = issueType in (epic, story)
username = username
password = password
disabled = 1
Configure which keys to display in the table with the keys, time_keys, and custom_keys fields.
jirarest:
Added a new "detail" option to the rapidboards mode that gives extra information about sprints or issues on the board.
Fixed a bug when a Label has the value "Label".
Fix an urlencoding bug in the JIRA REST command that broke search strings which contained special characters.
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 from Splunk, our partners and our community. Find an app for most any data source and user need, or simply create your own with help from our developer portal.