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
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.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs