Redmine

Thanks for the response.

After testing more, including on 2.6.5 and 3.0.3, I see what happened. When I set the custom field state to Required in Workflow, I did not do it for enough roles. In the end it seems like I needed to apply the setting to all roles for it to work as expected.

Not sure whether there is some issue in how the roles interact, or maybe the documentation could explain it more(?)

E Lipinsky wrote:

After testing more, including on 2.6.5 and 3.0.3, I see what happened. When I set the custom field state to Required in Workflow, I did not do it for enough roles. In the end it seems like I needed to apply the setting to all roles for it to work as expected.

Not sure whether there is some issue in how the roles interact, or maybe the documentation could explain it more(?)

You are probably testing this with a user account configured to be an Administrator. I've explained the expected behavior for this situation with references recently in RE: Validation on issue tracker before closing an issue?.
Another thing that might cause issues like this is that if a user has multiple roles on the same project, then only fields required/read-only for all its roles are actually required/read-only.

Hope this helps, Mischa.

Thanks Mischa, that does help. I think it was a combination of the Administrator and multiple role scenarios.

E Lipinsky wrote:

Thanks Mischa, that does help. I think it was a combination of the Administrator and multiple role scenarios.

I see. So this issue can be closed as it is the current expected behavior?

Mischa The Evil wrote:

I see. So this issue can be closed as it is the current expected behavior?

Ok, sure. Thanks.