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 MoreBRAVE, They woke up the Lion
It’s time to change, change your browser, change your searcher, it’s time to Web3. It’s time to wake up the Lion It’s time of BRAVE. The future is NOW! It’s BRAVE! It’s Web3! Faster, secure It’s time to change! The Lion, The Lion!… By MrAddon
Read MoreJira Groovy example to get values from a CASCADING custom field
Very useful example to get the values of a cascading customfield using Groovy in Jira.
Read MoreGroovy Script for JIRA to detect the last field change of a ticket
very easy, the trick is access to the class changeHistoryManager. Try this example in the “Adaptavist Scriptrunner” Script Console view. Just put the ID of the ticket and run the code. You will see always the last change of the issue.
Read MoreHow to set format to the value of a Custom Field calculated in JIRA with JIRA MISC addon
Very easy, first see this instructions to create the Custom Field To remove the decimal part of the resulting number from a division of two custom fields for example, and for adding the final character “%”, you can try to set in the “description” of the custom field (of type “Calculated Number”… for example) a…
Read MoreHow to restrict resolution options in JIRA
Very easy! Edit the Workflow transition to “CLOSED“ Click on “Properties“ Add this pair “key – value” jira.field.resolution.include = id_resolution_1, id_resolution_1023, .. That’s all!
Read MoreHow to Show/Hide Custom Field depend on another custom Field Value in JIRA
Copy this code in the description of a custom field (in the Field Configuration linked to the project)
Read More