All Apps and Add-ons

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

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

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

Splunk Employee
Splunk Employee

The capability needed is admin_all_objects.

0 Karma

Path Finder

Anyone in splunk have an answer to this ?

0 Karma
Don’t Miss Global Splunk
User Groups Week!

Free LIVE events worldwide 2/8-2/12
Connect, learn, and collect rad prizes
and swag!