Using a Server-side Validator to set the Fix Versions Required
When you mark an issue asResolvedwith the resolution ofFixed, you want the developer to specify aFix Version. However, it doesn’t make sense to require a fix version when the resolution isWon’t Fix.
Solve this using a server-side validator to mark theFix Versionfield as required, only when the resolution isFixed.
Create a new behaviour.
ClickAdd Field, and add theResolutionfield. Our server-side script, when written, is called the first time this field appears, and any time the user changes it in the dialog.
This example sets theFix Versionsfield to required and shown if the resolution isFixed, and to optional and hidden if the resolution is anything else.
To test the script,Resolvean issue. Experiment with changing the resolution value. TheFix versionsfield should change accordingly. A good experiment now would be to modify the script so that instead of hiding the field it’s made read-only. To do, changesetHiddentosetReadOnly.
If you have created a new behaviour do not forget to map it to a project, or project/issue type combination.
You might want to do something similar whereby if theDuplicateresolution is selected, theLinked Issuesfield is shown, if there not already aDuplicatelink for that issue.