Keep field required after transition

[Chad Waldman]

I have a field which I don't want required when an issue (Bug) is created. However, as part of triaging the bug, the field needs to be required. I do so by adding the required validator to my workflow when the issue transitions from Untriaged -> Triaged. 

The challenge I face is that people can still edit the field while the issue is in the Triaged state and remove its value. Is there a way to ensure that this field remains required upon editing even though I'm not transitioning the issue's status?

[Walter Buggenhout]

Hi @Chad Waldman,

Your options may be determined by the project type you are using (company managed vs team managed). The below solution works for company managed projects only, as only there you can define differents screens for create / edit / view. Since you talk about validators, that seems to be the case.

If you set up a screen scheme (see this support article for more info) with at least a separate screen for editing issues, make sure you have your required field on the create and view screens, but remove it from the edit screen. Just doing that will ensure the field is no longer editable for users after the issue gets created.

"Oh, but what if a mistake was made and the field needs to be updated afterwards?", I hear you rightfully say. You can still add a transition (Update required field x) and use a custom workflow screen with the field on it as a workaround for that use case.

Hope this helps! 

[Chad Waldman]

Thank you for your response. This will prevent editing the field unless you do a transition with a custom screen on transition. I'd still like to allow editing, just not removing the value once the bug is triaged.