Question regarding designing custom Jira sub-task

[tomas]

Hello,

We are using Jira Server v7.12

In every Jira ticket there is a possibility to create a sub-task by clicking "More" -> "Create sub-task".

My current understanding is that each company can implement many different sub-tasks which perform various tasks.

For example, in my company one of the most used sub-task in Jira is the retrieval of archived data from various servers. Jira sub-task provides the possibility for the end-user to set various parameters which determine the final output of the retrieved data which is then can be accessed on a back-end server.

But Jira sub-task menu is just a front end. In my given sub-task example, there must be some back-end code as well, which actually fetches the data, creates new directories, etc.

So my question is - how do I design my own custom Jira sub-task? Where do I start? Suppose that I have already written Bash/Python script on a back-end which provides certain info to the standard output or a file. Now I would like to somehow transfer that output to Jira front-end (whenever a particular sub-task is submitted), probably as a new comment. I am very new to Jira, so I don't know where to start.

And please note, that I do not have admin access to Jira. But I can write all the necessary code on the back-end and make it ready for Jira's consumption and then communicate internally with Jira admin to do the rest of the job. Are there any special requirements for back-end code in such cases? Is the language choice important? I code with bash and Python, and some Java.

Any guidance on this topic would be greatly appreciated.