If a script can do REST operations to a certain URL, it can certainly interact with JIRA through it's API, whatever that script is. You will just have to learn how that particular script implements it and use it against the JIRA API Endpoint for "Component" https://docs.atlassian.com/jira/REST/latest/#api/2/component
I suspect Walter may have been asking about the internal Jelly scripting, which was removed in JIRA 6.4.
The answer in that case was "no", as there were no tags for it (just add).
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.
It was old clunky technology that Atlassian didn't want to use or support any more. Most of the use-cases for Jelly were met by the new REST API, improving import functions and the automation plugin.
Jelly was also the only way that an admin could get into the heart of JIRA and break things without add-ons, so I suspect they wanted to close that option off as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.