Does making the "Componet/s" field "Required" through the "View Field Configuration" make the field

[Miroslav Preradovic]

Hello,

Does making the "Componet/s" field "Required" through the "View Field Configuration" make the field mandatory only on the screens associated with the projects that share the same field configuration, or does it make it mandatory for all screens that are associated with that field in Jira?

Thanks,

Miroslav

[Jack Brickey]

My advice - do not set components to Req in this manner or any field really. Rather, use the specific workflow and appropriate transitions and add a screen with the component field included. Then add a Validation for the transitionto require the component to be entered.

[Miroslav Preradovic]

Thanks for the advice! I actually decided against it, since it "felt" a bit dangerous. It affects too many things. I like your idea, but will have to wait till Monday to try it :)

Have a great weekend!

M. 

[Ravi Sagar _Sparxsys_]

Hi @Miroslav Preradovic 

Field configuration is assigned to a project using a scheme. So it is project specific. If the same scheme is being used by other projects then create a new Field Configuration Scheme.

Ravi

[Miroslav Preradovic]

Thanks Ravi!

My project's Field Configuration Scheme is shared by other 3 project, but that is fine as long as the field does not get changed on all the associated screens, which are MANY and most are not part of any of these 4 projects.

So I guess I am safe to make it required! :)

Thanks,

Miroslav