Different required fields for different request types sharing the same Issue type and fields.

Question

The needful fields are marked as required on the request form; however, when a ticket is created using CREATE button in Jira these fields aren't mandatory. To have consistency while creating a ticket using form/ jira CREATE button there is a request to mark these fields as mandatory depending on the request type.

At a workflow level - if I add a validator to make a few fields mandatory it is effecting all the request types using this issue type. I am looking to specify a condition of request type check and then impose field required validation.

We use Cloud, hence script runner behavior is ruled out. What are my options in achieving this?

Taranjeet Singh · Answer

@Hi@Kristian Walker _Adaptavist_ , It looks like @AtlassianAdmin is looking for a solution to make fields mandatory based on request types, not based on issue types, as the question mentions that multiple request types share the same issue type and same fields.

Could you please suggest any solution for that case using workflow validators in ScriptRunner for Jira Cloud?

@AtlassianAdmin Additionally, I would suggest to start looking for some other Marketplace apps for Jira Cloud as well that provide such workflow validators based on conditions for request types, may be "Jira Miscellaneous Workflow Extensions", "JSU Automation Suite for Jira Workflows", etc., that allow for such workflow customizations.

Hope it helps!

Kristian Walker _Adaptavist_ · Answer

Hi AtlassianAdmin,

I can confirm that you are correct that Jira cloud does not have the same behaviours feature currently that the server version has and so this means that your only way to achieve this requirement is with a workflow validator.

Workflow Validators use the Jira Expression Framework from Atlassian and I can confirm that in the documentation page here for the Jira Expression Framework that it shows that their is an issueType property which you can add to your expression to make it only run for a certain issue type and this will be the approcach to take to achieve your requirement.

I can also confirm in the example here on line 46 it shows how to use this issuetype property inside of an expression on Jira cloud.

I hope this information helps.

Regards,

Kristian