A lot of coding (scripting is one form of coding) has a steep learning curve most of the time, there is language, syntax, conventions and quirks to learn, and to get it right, you need to learn all of it at the same time. It looks scary.
Unlike human languages, where you can communicate meaning with another human with only partial bits of language (think of small children still learning their parent's language, or an international traveller who does not speak the local language), computers can't intuit what you might mean, and need you to be precise. You can't be precise without a good understanding of the language.
But the specific language does not matter much. What matters is your grasp of logic and your empathy with the listener. The computers are incredibly fast idiots. They have no intuition or empathy, they just do what they are told, albeit very very quickly.
Learn Python, C++, LOLCODE, Piet, Rust, machine code, or, or, or. Anything that gives you a grounding in how computers "think" will do. You'll find almost any language helps with scripting in Atlassian stuff.
Atlassian uses Java on the most part, and, as Ravi says, things like SR would be best to do in Java or related languages.
SR was mainly written for Groovy, but Groovy is a language that is Java-compatible, you could think of it as something that sits on top of Java. When I worked with @Ravi Sagar _Sparxsys_ , he was rightly critical of a couple of scripts I wrote/upgraded because I'm way behind him on Groovy and had written them partly in Groovy, then fallen back on my (much stronger) knowledge of the Java in the core of Jira when I wasn't sure how to do it in Groovy. My scripts were a hodge-podge of both - they worked and did the job well enough (i.e. reliable, correct results, and fast), but they were not elegantly written, and he helped me improve them - faster, and more readable at the very least.
Given that Cloud Jira has "Automation" and it is making its way into the other products (Confluence next, if I'm not misreading too much), I'd actually recommend a quick look at Scratch - I know it sounds childish, as a language designed to help kids learn to code, but the visual arrangement that it does is relatable to Automations, but it damn-well works.
There are young people in my family, ones being shown Scratch at school, and I'm the one who ends up with the more difficult homework questions on computers. Scratch makes it so easy to explain the logic side, but I got told off for going a bit off-topic by showing a god-child how her knowledge of Scratch might translate to Automation and then into coding later, and, given a bit of experience, a consultant and/or a community lead in a couple of years (she was 8 at the time)
TLDR: If you can show you can write working code/scripts in any computer language, and empathise with the computers, then you can easily adapt to other languages or scripts.
The computing industry does look for highly specific skills in some places (legacy COBOL or PRO-IV coders are my main examples of that), but generally, the language you choose really isn't going to limit you nowadays.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.