How to create custom issue type to automate access requests

Shivakumar Viswanathan_es04v6

I support a DevSecOps team that receives multiple access provisioning requests on a daily basis. People miss out on critical details when they create access request tickets in Jira. We waste a lot of time going back and forth. Is it possible to create custom issue types and automate the addition of a form or weblink to the Jira ticket being created?

For example:

Create an issue type "Action - Github repository access"

(this ticket should automatically contain a form that the requestor can fill with all necessary details)

Create an issue type "Action - Jenkins Access request"

(again, this ticket should automatically contain a form that the requestor can fill with all necessary details)

Create an issue type "Action - OCP access request"

and so on and so forth. 

So when the Jira card is being created, the person creating it would have the ability to pick the right access provisioning template to use which will also contain a form that they can fill with all necessary details.

Question 1: Does native Jira have the ability to offer this facility? If yes, how can I create these custom issue types and automate them?

Question 2: If answer is a No to question 1, what would be some of the alternatives available in the Marketplace? Any suggestions?

Thank you,

Shiva

Chris Buzon

Yes, you can do this by creating new issue types, and then creating "screens", "Screen-schemes", and "issue-type screen schemes" in order to surface the fields you need filled out per different use-case/issue type.

There are a number of ways to automate parts of the procedure, such as using Jira automation to fill in fields, or post-functions an validators to ensure tickets have required info (or set fields are required in the workflow or the field configuration). Jira automation is available on cloud to everyone - and it's incredibly powerful.
JMWE (Jira misc workflow extensions) is one I use almost every day for something.
Scriptrunner is likely able to do all of this, if you have some engineering time to dedicate to the task.

This type of functionality is also achievable in Jira Service Management, which allows you to create a more guided ticket creation process and queues for different purposes, pretty much exactly as you're describing.  It's a separate license from Jira though.

There are also several addons that can help with templates - my company uses one called Templates for Jira, and it's quite useful for creating various use-cases like what you're mentioning.

In short, this is doable in a whole bunch of ways, but none of them are exactly simple to implement unless you're already familiar with jira administration.