ScriptRunner - Custom Macros on the New Forge Platform

[Alastair Wilkinson]

I’m looking for feedback from ScriptRunner for Confluence users about a new way to access custom macros in the Forge platform. Your feedback will help us understand how disruptive (or not) this is to your current usage.

As we move ScriptRunner for Confluence to Atlassian’s cloud-based Forge platform, there’s an important change to how custom macros can be accessed.

Due to current Forge limitations, customer-created ScriptRunner macros can no longer appear as separate entries in the Confluence macro menu; instead, they must be accessed through a single, generic “ScriptRunner Custom Macros” option.

The only workaround* available to us is:

30 second video of the possible work around  

 Please answer these 2 questions in a reply/comment:

1. Will this workaround get the job done for you?

2. How easy or difficult do you think this process will be for you?
   (Please pick one.)
   1 – Very Difficult; 2 – Difficult; 3 – Moderate; 4 – Easy; 5 – Very Easy

*Important context

Right now, this workaround is the only available way to support ScriptRunner for Confluence Cloud custom macros on Forge, unless Atlassian adds support for Confluence dynamic modules on the Forge platform, so even negative feedback is useful to present to Atlassian.

Thank you for taking the time to share your thoughts!

[Tomislav Tobijas]

I mean, it's definitelly a difference in the navigation (to get to that specific user-created macro), but I don't see anyone who wouldn't be able to adjust. For sure, there would be some complaints, but we're probably talking about a minority of users. 

From my perspective (I haven't used this particular macro, but I believe some of my colleagues implemented it in a couple of environments):

1. This is sufficient enough
2. I'd go with "4 - Easy"

Cheers,
Tobi