-
Suggestion
-
Resolution: Fixed
-
4
-
As a rule writer
I want to copy and paste (clone) components within a rule
So I can rapidly create rules which have repeated branches, conditions, and actions
Acceptance criteria:
- Branch, condition, and action components can be cloned
- When a component is cloned, it is placed immediately below its source component
- When a branch is cloned, the child components of the branch are also cloned
- When a condition is cloned, the child components of the condition are also cloned
- Bonus: cloning can occur manually by editing a JSON rule file, leaving the component identifiers blank, and then importing the rule for a project.
Business case:
The user interface for rule automation allows rapid creation of rules in most ways, except for adding components. When rules have a repeated pattern, there is no work-around other than to add each component, one by one. Providing a component clone feature will dramatically speed up the creation of such rules.
***
Add an option to copy automation rules between projects -
We have 200+ projects mapped to our different clients, one project per client.
Each of these projects have the same automation rule set that is currently manually applied to them one by one.
An option to create the rule once and them copy it to another project will be very helpful.
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
-
- Closed
- relates to
-
- Closed
[AUTO-29] Ability to copy Automation rules and components (actions and conditions)
Can someone from Jira tell us ? I saw this functionnality last week and I was like : great it would have saved me a lot of time, and will do from now on, and it disappeared again 
Same! Saw it for a few minutes when I was spinning up some new automations, then couldn't find it again and became super sad again.
Very exciting though!
@Filippo Marchesi - I agree I noticed that working in my instance briefly. Maybe this is coming soon?!?
This worked for me last week, and now no more working..? I was able to duplicate a component and move it around. Now I can only delete it
Thank you c48be19ba6feand 8f52d8e96f65 for your responses. I agree I misunderstood the distinct issues and have changed the link between the two tickets to "relates to".
I have recently migrated a large number of Automation tickets that had been misfiled in other projects, into the Automation for Cloud project. I expect there will be some duplicates so please feel free to @ me if you spot any.
Thanks again for your assistance.
Anusha,
The AUTO-360 you linked appears to be for copying an entire automation rule from one project to another.
This AUTO-29 is for copying/pasting components of a rule while editing, such as conditions and actions, within an existing rule in the same project.
I have also voted on/watched the AUTO-360 that you linked but I would disagree that they are duplicates and protest closing one of them.
Hi Anusha Rutnam,
I believe your observations are incorrect. Please read this suggestion more carefully and you will find it is about copying the components of rules (actions, conditions, and branches) while editing a rule. The equivalent within an IDE would be copy-and-paste sections of code to support repeated patterns/logic in rules.
Please check with one of the automation product managers, or contact me, if you need more clarity.
Kind regards,
Bill
I believe this issue might be a duplicate of AUTO-360 – Ability to copy the automation of one project to another which has more votes.
I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I believe this ticket should be closed, but I will wait a week before taking any action in case anyone disagrees. Thank you!
Charlie,
I don't seem to have access to this link https://codebarrel.atlassian.net/browse/ACF-11182
This would be a great feature addition and save many unnecessary clicks. My mouse would thank you too 
Me too!!! Would save me a TON of work. Especially when I have to copy several fields from the Story to the multiple subtasks.
Please, please, pleeeeaaase! I just spent my last 3 days working on some more complex automations and I probably could have done it in 1/3rd the time if I'd been able to clone automation components. I'm doing a huge amount of repetitive work making "Create Issue" nodes and adding assignees and approvers and long lists of specific fields that only need minor changes between components. We're talking going from 50+ clicks to fewer than 10 clicks for each node with a clone option.
Hmmm.... It appears some of these ideas are already in the Code Barrel backlog:
https://codebarrel.atlassian.net/browse/AUT-781
https://codebarrel.atlassian.net/browse/AUT-1747
It would be great to have possibility to move any component through whole tree.
At this moment I see several problems, for example "branch" component cannot be moved from main level into deeper one. Or when you create branch component inside "if/else" then you cannot move it up/down within it. The same for "if/else" component.
It would be great to have the Ability to "Move branch rule created on the main branch and its component within an if-condition specified".
Hi everyone,
Great news – we have now released this feature! For more information please visit our community blog!
Thank you again for your feedback and suggestion!
Best,
Michael