Alternative for ScriptRunner JQL functions

Costel Ciocirlan

Hello everyone,

I am reaching out hoping that I might receive some advice from some of you. We will soon migrate to Jira Cloud from DC, where we currently have ScriptRunner installed.
The plugin was not used to so much in terms of scripting, behaviors etc. - what has and is still being used are the JQL functions that ScriptRunner offers.

Because we are not using ScriptRunner to it's full capacity we don't see a need to keep it currently.
The question that I have is: what alternative would you recommend to replace the JQL functions from ScriptRunner in the current DC environment and going forward with Cloud ?

I have found some other alternatives in the marketplace that I would want to test, but I just want to give it a shot here as well and see what other people from the community would advise based on your experience! 

Thanks in advance!
Costel

Amelie Winkler _Appfire_

Hi @Costel Ciocirlan – Amelie from Appfire here.

It really depends on what you're trying to do with those JQL functions and how customized your current Scriptrunner functions are.

One option you could check out is Appfire's JQL Search Extensions, designed specifically for handling JQL functions. You can use it, for example, to find issues based on user action, search for issues with Regex fields, find blocked issues or unfinished subtasks, and more.

Now even though the app has 50+ search extensions, it won't have the granularity you have with scripted functions. I suggest you have a look through the documentation and see if it makes sense for your use case.

Let me know if you have any questions!