If the transition that sets the resolution of the issues to "will not fix" and "not a bug" to another status that all the other resolutions, you could use the "Fields Required" validator on the other transition to make your field required in those cases. If all resolutions are brought together in 1 single status, I do not think it is possible to make the fields required in some cases and not in others. Depending on the type of field you prefer to be required, you could also consider to make it required in all cases, and just give it a specific value whenever the resolution is "will not fix" or "not a bug". Last option would be to have multiple transitions from the current status to the next, where you remove the resolution field from the transition screen in the cases of "will not fix" and "not a bug", and set the resolutions in those 2 cases through a post function. You can put all other possible resolutions in a single transition, where you DO add the resolution field to the transition screen opposed to setting it through a post function, and through the validator make the fields required that you need.
You do need to enable the JIRA Suite Utillities add-on in order for this specific validator to show up.
You could use the Groovy Script Runner plugin to add a little custom script to the validator.
https://jamieechlin.atlassian.net/wiki/display/GRV/Validators The examples in this link almost do what you need.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs