How to duplicate steps in JIRA Automation

[Akhil Mishra]

Is there any way to duplicate the steps in the JIRA Automation rule? In the below rule, you can see that after every If step, I have to create a confluence page. I have to do this for all components in my program so is there any way i can duplicate these steps so that i can just simply change the value instead of adding new step every time? 

[Walter Buggenhout]

Hi @Akhil Mishra,

That is a consequence of the low code automation setup. As an alternative,  you could consider using a scripting app (like Scriptrunner or powerscripts)  to build more dynamic use cases, but that does require scripting skills obviously to get going.

Hope this helps!

[Akhil Mishra]

Thanks @Walter Buggenhout 

[Bill Sheboy]

Hi @Akhil Mishra 

There are a couple of open suggestions to help with this use case, such as adding "copy components" and adding OR condition handling:

• https://codebarrel.atlassian.net/browse/AUT-781
• https://codebarrel.atlassian.net/browse/AUT-2036

For your question, what do you mean by "...so that i can just simply change the value"? 

If you mean to dynamically change the information provided for the Confluence page creation, perhaps you could either restructure your rule to get the information from the issue(s), or use a Created Variable to store the dynamic information and later use the variable with just one call to creating the page.

Kind regards,
Bill

[Akhil Mishra]

Thanks Bill, what I am looking for is an easy way to copy a step in the rule. In my program, we have around 30+ components and for each component i want to create a release page based on the even. Notice that there are some steps (marked with arrow below) which are almost similar but i need to every time create these steps. It would have been super awesome if there would have been an easy way to duplicate these steps and then modify based on the need.  

[Bill Sheboy]

Thanks for clarifying!  You mean you have 30+ "Jira Components" not "rule components", correct?

If so, you may be able to use an advanced branch over smart values to iterate over the Jira Components in the trigger issue.  This would make your rule significantly smaller, and most likely would not need a test for each condition.

https://community.atlassian.com/t5/Automation-articles/Branching-over-smart-values-in-Jira-Automation/ba-p/1741935

[Walter Buggenhout]

👍

[Akhil Mishra]

Thanks Bill. I thought of the Advanced Branch option but for my automation rule, there is a problem with it - I can't change the Confluence page setup location dynamically per component. So I need to use IF ELSE branching per component. 

[Bill Sheboy]

If your pages are all within one Confluence Space, you may be able to do this dynamically from your Components (if the names are aligned).  I believe there are some community posts on doing this from a rule, so perhaps search for those.  If that does not work from the Create Confluence Page action, I believe you could also call the REST API to create the page.