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

Custom field: how to configure as required for two diferent projects

Cristina_Roldan

Afternoon colls!,

I'm having a problem because I need to configure a Custom field as required for two diferent projects (A & S) but I don´t know how to do it.

A project has this custom field as required but I can´t configure it for S project.

The issue types are different for both:

Could you pls help?

Thanks in advance

Accepted answers

Jakob KN

Hi Cristina,

How are the configurations different between the two projects, and which type of field is it?

If you just need to make the field mandatory, you'll be able to do this through the field configurations.
If it's only to be mandatory for some issue types in the project, you can define different field configurations for different issue types, through a field configuration scheme.

All comments

Jakob KN

Hi Cristina,

How are the configurations different between the two projects, and which type of field is it?

Aditya Sastry

Hi Cristina,

There are different ways to make the field mandatory. Like Jakob suggested, simplest way is to do through field configuration.

If you need these fields to be mandatory at any specific step, you can use validators.

Let em know if you need more information.

Cristina_Roldan

Hi colls!

thx for your fast answer.

On Field Configuration I have this

Aditya Sastry

so field configuration is a bit confusing, if you are new. This doesn't mean that it is required for all the 3 screens. It maybe required for only one among all the screens shown.

Jakob KN

Hi again!

So whichever project this field configuration is applied to, should have the Referer field mandatory.
Different issuestypes withing the project can have different field configurations mapped to them, so you'll need to check if that's the case in the project

Note that the screens shown in the field configuration just lets you know where the field is used, it doesn't mean that the field is necessarily mandatory on those screens this still depends in the individual field configurations for the projects. (a bit counter-intuitive, i know).

Cristina_Roldan

Hi everyone!!

I've checked again the field configuration and now is required, apply for both projects.

Thanks a lot for your help!

Jakob KN

Good to hear!
Feel free to accept one of the answers, so others can see that the question was resolved if they have the same issue.

Welcome!

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

Quick Links

Find more posts tagged with

custom-field

jira

cloud

jira-cloud

required-field