Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Can ScriptRunner be used as an alternative to standard plugin development?


I've been tasked with evaluating whether or not ScriptRunner (for Confluence) could be used to add functionality and extend Confluence in place of the regular plugin development method.  From what I can see, yes, but only in a limited way.  With SR, I can create some of the module types such as Web Items, Web Sections, Web Resources, REST endpoints, etc., but only on an individual basis whereas a single plugin could incorporate many of these web modules and more in a self-contained package (jar).  To migrate a moderately complex plugin consisting of several modules would require one to create each of those modules through SR on their individual screens, and if that could be done, great.  But, once you have several plugin code migrated to SR, I'm guessing it could get messy trying to remember which modules and scripts work as a group.  Also, SR, does not support all the module types available to plugins, so that would be another drawback.

Sorry if this is an unusual question and thanks in advance for your response.


1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

1 vote
JamieA Rising Star Mar 30, 2017

People use script plugins to draw together the various components that make up a particular "solution". They contain the code plus any necessary configuration. 

Yes you are right in that not every area is covered by a simpler scripting interface, but in that case you can also include any plugin extension point in a script plugin, in the normal way. You can write those extensions in groovy or java as you choose.

When you get to require quite complex plugins, classloader problems can cause diminishing returns and you may as well write a regular java plugin. It all depends whether the dev speed advantage is worthwhile to you or not.



AUG Leaders

Atlassian Community Events