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

Field configuration

Hi friends,

I have 2(issue type1, issue type2) issue type and 2 (screen1,screen2)screen. During create the issue based on both issue type(issue type1,issuey type2) one screen(screen1) displayed and Then another one screen(screen2) displayed during edit based on both issue type(issue type1,issue type2). Only 2(field1,field2) fields are different for both screen, during create the issue the field (field1,field2) does not displayed but during edit the issue the fields(field1,field2) will be displayed.

Now i want to make those 2 field(field1,field2) mandatory during edit the issue based on those issue types, it is possible. I do not how to make the field configuration,Please help me.

Thanks in advance,

Karthik a.

Accepted answers

Jobin Kuruvilla [Adaptavist]

You can't make a field mandatory just for one screen. If the field is made mandatory using field configuration, it will be mandatory right from 'Create', even if the field is not present on 'Create' screen.

An alternative would be to allow editing of that field only via workflow transitions and in that case you can make the field mandatory using workflow validators. Javascript hacks is the other option.

All comments

Jobin Kuruvilla [Adaptavist]

An alternative would be to allow editing of that field only via workflow transitions and in that case you can make the field mandatory using workflow validators. Javascript hacks is the other option.

Hi jobin,

Thanks for your updates, I make the two fields mandatory and i could not include those fields in create screen. Then i tried to create the issue it shows those field are required but in the create screen those fields are not available.

Thanks,

Karthik A.

Jobin Kuruvilla [Adaptavist]

Yes, that is what I was trying to say. That is just how JIRA works.

Joe Pitt

If you want to require them after creation you need to require them on a transition with a plugin like jira-utilities. The resolution field is ALWAYS required when put on a screen regardless of the field configuration. That is why it should only be put on the transtion screen when you want to set it.

RambanamP

As @Nic suggested, add the global transition something like "Update Data" and add those fields to this transition and remove the fields from edit screen so you can make fields requires using validator

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-cloud