With Adaptavist Scriptrunner or MyGroovy plugins for Jira Server and a little groovy script we can validate/require or make mandatory the second drop down of a cascading field. Just create a Simple scripted validator in the transition! Example: Very easy! Example: By MrAddon
Read MoreAnyone else hate the new Jira Cloud “mandatory” experience?
This post is the continuation of: Atlassian is obfuscating Jira Cloud!!! ¿¿Why?? I’m relieved to see that I’m not alone in my suffering… See more comments here: https://community.atlassian.com/t5/Jira-questions/Anyone-else-hate-the-new-jira-experience/qaq-p/684161 The same comments in SPANISH here: https://translate.google.es/translate?sl=en&tl=es&u=https%3A%2F%2Fcommunity.atlassian.com%2Ft5%2FJira-questions%2FAnyone-else-hate-the-new-jira-experience%2Fqaq-p%2F684161 By MrAddon
Read MoreShow/Hide Mandatory fields in Jira dynamically with Behaviours
It’s very easy to do in Jira Server with the help of the awesome plugin Adaptavist Scriptrunner. Just create a new Behaviour ( press “.” and write Behaviours). Associate the Behaviour to your project (and/or issuetype/s). And the click in “Fields” to add the field you want to “observe”. For example, custom field “Jira Category“.…
Read More