Jira Automation programming

[Ray Albert]

I just received a eval copy of Automation as we are migrating towards the Cloud in a year and wanted to get an understanding of the Automation scripting.  I have decommission process flow, where 

1. a person creates a Jira epic/support ticket.

2. when the ticket is created it creates another ticket for approval. (which i have done).

3. Now this is where i am needing assistance.   Once the approval ticket is set to done, i need for another ticket to be created in the same epic/support ticket as the in step 1.  Can this be done in the same trigger or do i need to create another trigger to do that. 

4. Is it possible to setup a list of approvers for each employee that Jira can read and populate the approver as it is creating the approval jira ticket?

[Bill Sheboy]

Hi @Ray Albert 

Do you mean Automation for Jira?  If so...

For your item #3: this could be done with a separate rule, triggered on the approval ticket transition.  That rule could identify the parent and add another one linked to it.

For your item #4: you may set up that list of approvers as a group for assignment, hard-code the list in the rule, or use a longer if/else structure to perform the assignment.  The specifics of what is possible require more details about your use case to learn if there are problems.

Here are some links to documentation and example rules to get you started on your investigations:

• https://www.atlassian.com/software/jira/guides/expand-jira/automation
• https://www.atlassian.com/software/jira/automation-template-library#/
• https://community.atlassian.com/t5/Automation-articles/Jira-Automation-all-the-resources-you-need-in-one-page/ba-p/1388465

And for the Jira Server/Data Center version of automation, here is a specific link as that version has some differences from Jira Cloud: https://confluence.atlassian.com/automation/automation-for-jira-server-7-4-documentation-993924595.html

Kind regards,
Bill

[Ray Albert]

Thank you for the quick reply. 

You are correct Automation for Jira.

I will review the documentation and see what I can understand. I am just thinking that all of these are triggers are global and how do you keep each ticket tied together.  I am guessing that is where the Parent info comes into play.