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

How to make fields mandatory

Kian Pariwar

Hi,

I read a lot about making fields mandatory and found 2 ways:

Set fields to required
Set validators in the workflow

I wanted to go down the "required" route but it did not do anything. Therefore I do not understand the point of it at all. E.g. if I set the default field "Due Date" to required, I still can create an issue and leave the due date blank and progress along the board. Am I missing something?

Instead I opted for validators in my workflow, which was pretty extensive work but it works.

Nevertheless, I would like to understand why field configuration does not work. And yes, I created a field configuration and a scheme for it and assigned to the right screen.

Any feedback would be highly appreciated.

Regards

Kian

Accepted answers

Nic Brough -Adaptavist-

>And yes, I created a field configuration and a scheme for it and assigned to the right screen.

No, you did not. Field configurations have nothing to do with screens. They are grouped together into "field configuration schemes" that associate them with issue types, and then projects use them to determine which field configuration to use for their issues types.

That's what is missing - I doubt you've associated the field configuration correctly.

All comments

Jonas Fitz

In a Workflow transition you can set up validators. One of these Validators is that a field needs a value or have to be changed during transition.

Nic Brough -Adaptavist-

>And yes, I created a field configuration and a scheme for it and assigned to the right screen.

That's what is missing - I doubt you've associated the field configuration correctly.

Kian Pariwar

Hi Jonas,

I know that. That is the second way I opted for and it works fine.

But I just want to understand the point of field configurations. Everywhere it says in the documentation that in order to make field mandatory I need to set a field to required. but it simply does not work. am i doing something wrong?

Nic Brough -Adaptavist-

Again, check the project settings and scheme. As you can't associate them with screens, I think you've got that confused.

Kian Pariwar

sorry, my mistake in wording.

just to be clear:

I defined a custom field, assigned to several issue types (6) and 1 screen.

This field is configured within a field configuration as required. This Configuration is part of a scheme. For testing purposes I only assigned the field configuration within the scheme to 1 of the 6 issue types.

With this setup, setting to required does not do anything.

Nic Brough -Adaptavist-

There's no mention here of using the scheme. Setting up a scheme is fine, but you have to actually use it.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud