I have a user who's asking if it is possible to make the Comments field mandatory when changing the "Fix versions" field on a ticket in a Classic/Company-managed project.
This is not like using workflow validators or making the field required in the scheme, but rather when a ticket is created, and at some point in its life cycle, (e.g. during an "In progress" state) the "Fix versions" field is changed, they want there to be a comment required in order to document why there was a change.
The issue is that developers are changing the field and not putting any comments or documentation in the ticket, and so the versions are bouncing all over the place and causing issues with reporting and organizing bug fixes.
We're on cloud version. I checked similar requests but they point back to a validator, or required field, but that doesn't help with already active tickets that may not necessarily change their status (which I understand is what the validator would need) or a ticket create (required field).
I've thought about perhaps an automation to alert the Reporter, etc. when there is a change to the Fix versions field, which might be a good start if that is possible. Any thoughts on this option?
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.