rbeckman-nextgen
commented
4 years ago Even if the only change was to make cloned channels stay in the Channel Group they were cloned from, that would be amazing. As it is now, we're managing over 100 channels; having to scroll back to the top of the list and drag the channel down multiple pages of scrolling to put it back in the Group the original channel is in gets a bit frustrating.
Imported Comment. Original Details: Author: jridderhoff Created: 2019-11-22T07:57:28.000-0800
Related to [MIRTH-4195] and [MIRTH-4196]. Currently the clone channel dialog only asks for the name of the new channel.
It would be very helpful to have options for cloning dependencies (resources, code templates, channels.) I can see there being times where it would not be desired to pick up the same dependencies, but most of the time that's what people expect to happen. Possibly implement with an "Include Dependencies" checkbox option, that when checked enables a button that opens the "Channel Dependencies" Dialog, pre-populated with the cloned channel's dependencies.
Likewise, a drop-down selection for the channel group would be helpful, with it defaulting to the same group as the cloned channel, instead of automatically placing it in the "Default" group.
It looks like tags are automatically copied already. That would be nice to have as an optional setting as well.
Having these show up as options in the clone dialog is also a good reminder for the developer to review all of these settings when cloning a channel.
Imported Issue. Original Details: Jira Issue Key: MIRTH-4330 Reporter: agermano Created: 2018-09-20T09:53:19.000-0700