I'm interested to know what are the options when it comes extending JIRA Server without having to use official Atlassian SDK with Java.
I would also like to know Atlassian's stance when it comes to third party add-ons that allow to execute arbitrary code inside JIRA Server. Whether they support such add-ons or prefer people using their official SDK? I just don't want to end up in a situation when I have invested heavily in some unofficial scripting solution and in the future Atlassian decides it's time to block everything that is not developed using their official SDK.
The addons, which you mentioned , are actually all based on Atlassian SDK. They just provide you entry points to Atlassian SDK without making you write your plugin but those addons are all plugins.That is why I think there is no point to block such addons.
And using these addons also depends on your needs. It is simpler to make a good development procees writing plugins than using scripting addons. By good development process I mean continuous integration, continuous delivery and continuous testing. I devoted lots of my time to these tasks. And plugins are more suitable for this. But scripting addons let you do stuff very fast. That is why when I choose what to use I estimate mantainance cost and development time. I think the best way is to combine scripting and plugins in your solutions.
I'm not looking this solution for my myself, I already have extensive Atlassian SDK experience, I'm just looking for a solution for colleagues who would like to do some additional scripting with the minimal entry barrier, that's why I asked if JS like syntax scripting exists as the chances are those people already have JS experience.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG