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

After change the field "performer" is Required

Anton BIRILLO

HI all ! now faced with the following situation in jire v4.3.1:

After change the field "performer" is Required (for screens: Resolve Issue Screen, Test Issue Screen in Field Configuration), at the time create issure an error (they say it is required field):

but the screen to create issure (Create Issue Screen), I did not put this field as required.

the guys in what could be the problem ?

Accepted answers

Udo Brand

From your second screen shot I can see that Performer is a required field (like Priority below). The documentation says required fields are validated and needs to be on the Create Screen.

If you want to make this field only mandatory in the later process then make the field optional and use a field required validator in your workflow (see link in C. Faysals answer)

All comments

C.Faysal {CFcon}

i don't see the field "Performer" on your issue create screen

is there a validator set in the workflow ?

https://confluence.atlassian.com/display/JIRA/Using+Validators+to+Make+Custom+Fields+Required+on+Transition+Screens

Anton BIRILLO

C.Faysal All right, we do not have this field on the "Create Issue Screen", but even if it set,

error is presented:

Anton BIRILLO

plugins installed only two : JIRA TimeSheet Plugin, jira-status-color.

C.Faysal {CFcon}

yes i see...thats what keeps me wondering.

do you have any plugins like behaviours or jira suite installed?

Udo Brand

From your second screen shot I can see that Performer is a required field (like Priority below). The documentation says required fields are validated and needs to be on the Create Screen.

If you want to make this field only mandatory in the later process then make the field optional and use a field required validator in your workflow (see link in C. Faysals answer)

C.Faysal {CFcon}

exactly...i totally missed that point.

Anton what are you tryin to achieve? who should be "Performer" ?

maybe we can figure out sth with a post-function for the "resolve" transition and the "Update Field Value" setting

Anton BIRILLO

I want whatever is achieved in the field "Performer" was required only when the process issue workflow step:Resolve Issue, Test Issue. in all other "optional".

Udo Brand

So add a field required validator in those transitions (add a transition screen with that field as well) and make the field itself optional. That should fit your needs.