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

Priority mandatory

Daniel Juravski

Hi,

I added to the 'Priority' field new priority named "None", I would like to make the 'Priority' field mandatory, such that the user will have to pick some option of the priorities and not leave the "None" priority as it.

How can I do it ?

Thank you.

Accepted answers

unknown

Welcome to the Community @Daniel Juravski!

You can define the field behavior with field configuration schemes.

All comments

Yogesh Mude_u145qk

Hi @Daniel Juravski

Make this priority field as a Required using field configuration scheme.

https://confluence.atlassian.com/adminjiracloud/configuring-a-field-configuration-scheme-844500805.html

Grigory Salnikov_0hffsd

Hi!

I'm sorry, but why adding a "None" option in the first place?

Regarding your question, you can only make a field mandatory, not the value in it.

Daniel Juravski

Hi @Yogesh Mude,

Even when the field is required, its automatically gets the default value of 'Priority', thus the user doesn't really need to insert its value to it.

Grigory Salnikov_0hffsd

That still leaves us an option to choose "None"

unknown

Welcome to the Community @Daniel Juravski!

You can define the field behavior with field configuration schemes.

Daniel Juravski

Hi @Grigory Salnikov,

Pls. see my answer to @Yogesh Mude

Daniel Juravski

The 'None' option was to force the user to insert its real value for 'Priority'.

Daniel Juravski

Hi @[deleted]and thank you !

I know how to define a mandatory behavior to a field, however my problem is that even when the 'Priority' field is required - it has already a default value, what makes it not really mandatory.

unknown

@Daniel Juravski,

It is currently not possible to default the Priority Field Value to NULL (non-selected).

Your request makes sense and others have requested this before. Feel free to comment and vote for this suggestion: Allow 'No default' for Priority (JRASERVER-13048).

A 'dirty' solution would be to create a new priority (called 'Please select' or 'Unselected') and set it as the default. You can then add a validation in the Create transition to verify that the field value was changed (this may require an add-on).

Robb F Watkins

@Daniel Juravski Did you ever get this resolved. I have the same issue. What about seeing if the field changed from a default value like "None" Priority Assignment.png

Daniel Juravski

Hi @Robb F Watkins,

I did resolve it. I added the 'none' value (in your case - 'ENTRY PRIORITY'), set the priority field as a required with the 'none' as default.

Then, on each issue type that I wanted to force the priority choice, I edited its workflow such as the create transition will has a validator that checks if the priority value is not None (I used the ScriptRunner add-on with the next command: issue.priority?.name != 'None')

Robb F Watkins

@Daniel Juravski Wow. That is so simple I am almost embarrassed for asking. It worked like a champ. Thank you!

Daniel Johnson_holard

@Daniel Juravskiyou saint! I got just as far as you and @Robb F Watkins without even thinking of scripting the validator to make it required to have another option other than the "None" priority I created. Thank you!