Yes, there's an "excute" method you can use on strings, which is a bit inelegant, but a starting point. For example "ls -l".execute()
But, you'll almost certainly be wanting to trap any output and probably store it if you're doing that, and that gets more complex.
You mention SQL as well - that's also possible, although I'd let the system do the work - if you have the right driver installed, groovy supports execution of SQL via that.
However, I'd want to ask "why"? If your SQL is to be run on JIRA data, then there's actually a good chance that you should not be doing it at all.
Thanks for the support!
My case is:
On the SQL-server we have two DB: one is JIRA and other it is our own. My need is to insert/update data in our own database when issue is being moved or when there is a custom event.
Is there a way to not do it (e.g. with Groovy or etc.)?
Yes, I'd use Thanos's example code to create a connection to the other database.
My fear (which happens too much) is that you might be trying to write to the JIRA database - don't ever do that. Updating your other database from JIRA is fine (assuming it's not sensitive like JIRA rightly is)
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot