nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can a field been made mandatory depending on request type.

siva_xx9qs1

For a transition from A TO B,

i need a custom field (ex: TYPE) Mandatory depending on request type.

Accepted answers

Patrick Cartier [Candylio]

Hi @siva

I would suggest creating an issue type for that request type, a transition screen with the required field, and making that field required on transition with a validator.

Otherwise you are going to have the field required for all request types that use that issue type.

All comments

Patrick Cartier [Candylio]

Hi @siva

I would suggest creating an issue type for that request type, a transition screen with the required field, and making that field required on transition with a validator.

Otherwise you are going to have the field required for all request types that use that issue type.

siva_xx9qs1

The task is not to create a new isssue type, but neet to make the field mandatory depending on request type.

thinking of using any script validator.

THANK YOU.

Patrick Cartier [Candylio]

Well, that's the way I would do it without any add-ons. Since Jira doesn't relate workflows or required fields to request types outside of the portal.

I found a workaround here that uses scriptrunner:

https://community.atlassian.com/t5/Jira-Service-Desk-questions/Using-Customer-Request-Type-in-a-Workflow-Condition/qaq-p/709177

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

post-function

workflow

addon-com.innovalog.jmwe.jira-misc-workflow-extensions

automation

pull-request