Limit Customer Request Types By User Group In Jira

[David Harkins]

Is there a way to limit the available Customer Request Types as part of a behaviour?

Trying to to get this working at a basic hardcoded level first 

LinkedHashMap optionMap = [:]

optionMap.put("-1", "None")

getFieldByName('Customer Request Type').setFieldOptions(optionMap)

But cannot get this to work yet.

We have been limiting which Issue types can be raised from the blue create button in Jira,

Now we need to the same for the Request Types, as some should only be raised via the portal.

[David Harkins · Accepted solution]

I managed to get this working in a different way, by means of checking is a user is a Group or Role.
If they are, and it meets the criteria for that request type, the fields for that request type are set as required. (Visible, Read Only, Form Value, Label, Description).
if not, all other fields remain hidden and an error is displayed stating the user does not have access to that request type.

[Ram Kumar Aravindakshan _Adaptavist_]

Hi @David Harkins

Unfortunately, this is not something that is doable via ScriptRunner's Behaviour.

It's not possible to restrict the Request Types via the Behaviour mainly because the Behaviour only works for Create / Edit / Transition and Assign screens.

The Request Types do not appear on any of these screens for the Behaviour to control it.

Thank you and Kind regards,
Ram