When and how to use the canned ScriptRunner script 'Configuration exporter'?

[Rina Nir (AC)]

JIRA 7.1.9

ScriptRunner 4.3.9

I noticed there is a (new?) canned script called 'Configuration Exporter', and as moving configuration between instances is always a hot-topic I wanted to explore what it does.  My impression was that it facilitates exporting of some ScriptRunner related items (at least listeners- which was the only item type this instance had) and generates .yaml code.

It then said: Copy and paste the following to your script-runner.yaml file

Fair enough. However- I could not find any doc explaining how and to what end I should use this yaml file.

Is there any documentation available which I missed?

[JamieA · Accepted solution]

Hi Rina...

Docs are here: https://scriptrunner.adaptavist.com/latest/jira/creating-a-script-plugin.html

Also https://scriptrunner.adaptavist.com/latest/jira/DevEnvironment.html has been worked, which is a precursor to creating script plugins.

[Rina Nir (AC)]

Thanks for teh speedy response

So, that's what I understand:

1. You have scripotrunner bit as 'inline' scripts in your dev instance.
2. The tool automatically finds those items and creates a .yaml export
3. Which can be packaged into a ScriptRunner plug-in and installed on prod.

Would be nice to have something mentioned here also: https://scriptrunner.adaptavist.com/latest/jira/builtin-scripts.html

[JamieA]

Not just inline, either inline or file. 

New built-in scripts can be added too. There are examples here: https://bitbucket.org/Adaptavist/scriptrunner-samples/src/d6e4a04c5d1d1721a270168ed79ed8f604079c79/jira/test-plugin/?at=master

The admin built-in script example is at https://bitbucket.org/Adaptavist/scriptrunner-samples/src/d6e4a04c5d1d1721a270168ed79ed8f604079c79/common/test-plugin/src/main/groovy/com/onresolve/scriptrunner/canned/common/admin/DependentCannedScript.groovy?at=master&fileviewer=file-view-default 

[Rina Nir (AC)]

Yes, I notice now that the plugin example also has a yaml file in it!

[JamieA]

Yes... the yaml file is only requred for stuff that you configure through the UI, eg listeners. Built-in scripts are just found through classpath scanning, so they only need to be present (with the right package, currently).