Option to clone a trigger / queue


We use triggers quite often which have slightly different inputs (robots / process / process parameters) both in development and production orchestrators. Similarly we also create multiple queues for a single process. A clone feature for queues also could make this easier. The queue properties will also require minimal change from the users.

Currently, hamburger menu on a trigger shows the following options.

Currently, hamburger menu on queue shows the following options.

A cloned trigger needs to be in disabled state to avoid unintended job runs and contain a suffix to the name to ensure no clashes occur with the original trigger. The cloned queue name can also have a suffix.