You know, I want to have that conversation with @Jamie Echlin [Adaptavist] as well. I suspect the answer is going to be a resounding "no", because the script runner effectively allows an admin to inject code, and that can be a disaster in the hands of an inexperienced admin. As Cloud is hosted, the last thing a host wants to do is hand the users a tool that could destroy their installation and then be asked to fix it!
However, I know he's looking into modular permissions, so that you can write a script and use it without being an admin, so I could see a version in the future where the script runner could be enabled in Cloud, with a pre-selected list of scripts that Atlassian Cloud Admins can test, commit to supporting, and restrict you to.
But I don't know if that is the plan.
Actually, we just want the JQL features in this plugin. It'd be great if Jamie Echlin could separate the JQL part into its own plugin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good question, I don't know if the JQL is entwined with the script runner in any way.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dave M just closed tha jac request for this feature
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah it's this one: https://jira.atlassian.com/browse/JRA-41869. The JQL functions will be split out at some point, mostly for other reasons. But I don't think that will sway Atlassian, AFAIK there is a blanket ban on any new P2 plugins in Cloud. And a cloud version is not really feasible with the current state of P3.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.