I have a request type that I need to add a validator to. The request type uses the same issue type and workflow of several other request types and I do not want to apply the validator to all of them; just the one request type. When I configure the validator to require a certain field that is specific to the request type, it applies it to all request types even though they don't contain the field. Hope that makes sense. Is there any way to do this?
Hi @Cindy Blanton ,
validator, as you said, is at issue type level and it impacts all issue types defined in the workflow scheme. My suggestion is to create a specific issue type and map it with the request type. Then copy of workflow, apply your validator and edit the workflow scheme in order to map the new issue type.
Hope this helps,
Fabio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I also have the same requirement,
A new issue with a new duplicate workflow would lead to issues further down the line when attempting to keep workflows in sync.
As part of the Validation process, we should extract the name then make any checks for that request type within a singular workflow.
Just attempting to work out how best to get the Customer Request Type Value as part of a Validation Script.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is possible with a Jira expression-based validator. I have just checked the following expression, and it blocks the transition for the selected request type when additional conditions are not met:
customerRequest.requestType.id == 34 ? issue.dueDate != null : true
There are several apps available on the Atlassian marketplace, that will allow you to do it.
I am from Forgappify, and we developed Jira Expression Validator, which is part of the Workflow Building Blocks for Jira free app.
I would appreciate it if you could give it a try.
I am leaving a link to the app's documentation if you are interested.
Kind regards,
Maciej
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To supplement what @Fabio Racobaldo _Herzum_ suggested, it is important to know that in JSM that request type(s) uses Issue Type as the based, and WF setup is applied at the Issue Type level.
Hope this also helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Technology Applications Team
Viasat Inc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.