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; } } }

Making a field non-mandatory using ScriptRunner scripts

Tayyab Bashir

Hi,

I have a field mandatory in couple of projects sharing a single workflow.
I am making this field mandatory using workflow validators on create issue screen for all these projects.

Now there is a project (ABC), and I don't want the field to be mandatory in it.
Could someone tell me how to do that?
How can I make an exception for that project without disturbing all the other projects?

P.S. Creating a new field configuration is not ideal for me. And would be the last approach.

Many thanks,
Tayyab

Accepted answers

Nic Brough -Adaptavist-

Field configurations make field mandatory from creation time, so I assume you're using validators because you need them optional for part of the lifecycle. (If you need them mandatory throughout, then you absolutely should be using field configurations)

So, the simple approach - copy the workflow in use, put it in a new workflow scheme for the new project, and strip the validators out of it.

All comments

Nic Brough -Adaptavist-

So, the simple approach - copy the workflow in use, put it in a new workflow scheme for the new project, and strip the validators out of it.

Vasiliy Zverev

I would reccomend to use field configuration scheme beacause it garantee that after creation value for these fields will not be set to null. And these make it simpler to use the same workflow into different projects.

Sachin Dhamale_9u8xx5

If you want to use script runner plugin then You can use a behaviour section to make a field mandatory for a specific project and issue type

Tayyab Bashir

I created a new field configuration, but since the fields are being made mandatory using a workflow validator, I can't make them optional with the new field config, right?

Tayyab Bashir

I would need to create both a new workflow and a new workflow scheme for it?

Vasiliy Zverev

You are rigth. That is field configuration for. You have the same workflow, but different mandatory fields into different projects.

In your case I would reccomend you to define where to reasilse logic for mandatory fields: into field config or into workflow validator.

Benefits for field config:

mandatory fields will not be made empty
will be marked with red star on create screen
more flexible to use into different projects

Nic Brough -Adaptavist-

Yes, that's one of the things workflow schemes are for - to allow issues to follow different processes.

Nic Brough -Adaptavist-

Plus, with field configs, you can carry on using the same workflows.

Slava Gefen

Hi @Nic Brough -Adaptavist- !
In our server Jira we have a mandatory field and it has to be mandatory indeed. We did it with field configuration. But there is only one case we need this field not mandatory - when there is a specific label. e.g. "NotRequired". Is there a way to avoid this mandatory rule during creation an issue using Scriprunner only in this specific case?
Something like this:

def label = labelsField.getValue() as String
def isLabel = label == "NotRequired"
customfield_12345.setRequired(! isLabel)

Can I use it as a post-function during creation?

With kind regards
Slava

Welcome!

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

Quick Links

Find more posts tagged with

scriptrunner

jira

jira-software

jira-administration

scripted-field