We are in the midst of upgrading our JIRA instance along with upgrading the very awesome ScriptRunner to version 3.0.7.
In our previous version of scriptRunner (2.1.15) Administrators could selectively disable the build-in Script Functions, however, in the new version I can't find a way to explicitely disable some of these built in script functions.
Anyone know if it's still possible?
Thanks for the response Jamie. I liked the idea of making them administratively disable-able since it provides the most flexibility for an admin. In the past I have had to disable two functions (issueFieldExactMatch and issueFieldMatch) because my users found creative regular expressions that could be used bring down our system. I'd have to dig up the exact queries used, by I remember the system ran into memory problems.
Well that is good news....because users did love the functionality. :) We'll give it a whirl in our upgraded instance and do some testing. BTW, I've just upgraded my custom JQL functions using your guide for moving to 3.0. It was invaluable and I wanted to thank you for putting that together. Cheers. /rt.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
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