All Apps and Add-ons

What additional permissions are needed for a non-admin user to create JIRA tickets?

sidekix24
Path Finder

We are using JIRA Custom Alert Action : Ticket Creation in the Splunk Add-on for Atlassian JIRA Alerts. Adding the action to create Jira tickets are successful when the admin is the owner of the created alert. When we use an alert where the user is a non-admin, we get the error below:

Audit:[timestamp=12-20-2016 17:30:08.016, id=1394473, user=XXXXXX, action=list_storage_passwords, info=denied object=":jira_password:" operation=list][h3cPe0IMF3dhD6bfVXuXWZTXTCcGP5owR/QOitXRH5RMYviW/Cm3SXixpBS/aoCEFGgqGhp4IA8+CrSPl6zgd9fr/DUtURoL55hnE843tk3fUTz9wCtxmgYtvDQEAoPg88qD43M6lZiGH/ywWQ79yZqAvfYCyUx5xvtbec8TOx0=]

Does anyone know what capability we need to assign this role or if it's another permission that needs to be saved?

We gave the role that the user is assigned to the list_storage_passwords capability but we still got the same error.

Thanks

0 Karma

gavsdavs_GR
Path Finder

(I'm pretty sure) We've done it without giving users admin_all_objects - we just made all the artifacts in the jira alerting app world readable, and we use an account to post into jira that's only allowed to post into jira and nothing else.

Our jira projects are independently permissioned.

0 Karma

tpeveler_splunk
Splunk Employee
Splunk Employee

The capability needed is admin_all_objects.

0 Karma

gavsdavs_GR
Path Finder

Anyone in splunk have an answer to this ?

0 Karma
Get Updates on the Splunk Community!

Introducing Splunk Enterprise 9.2

WATCH HERE! Watch this Tech Talk to learn about the latest features and enhancements shipped in the new Splunk ...

Adoption of RUM and APM at Splunk

    Unleash the power of Splunk Observability   Watch Now In this can't miss Tech Talk! The Splunk Growth ...

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...