Cloned channels should inherit any channel dependencies

[rbeckman-nextgen]

Similar to MIRTH-4195, if a channel has any dependencies and the channel is cloned, the new copy of the channel does not also have those dependencies. In order for the new channel to be functional (with no other changes), the dependencies must be manually-added to the new channel (which is performed in a different place in the UI).

It violates the principle of least surprise that a newly-cloned channel might not work because of the failure to copy the dependencies of the parent channel.

Imported Issue. Original Details:
Jira Issue Key: MIRTH-4196
Reporter: [email protected]
Created: 2017-07-19T13:50:25.000-0700

[rbeckman-nextgen]

+1 for this. Cloned channel should also go into the same group as the cloned channel. If not edited after cloning, a cloned channel should be identical to the original except for the name in every way.

Imported Comment. Original Details:
Author: jtd
Created: 2020-05-01T06:01:50.000-0700

[rbeckman-nextgen]

I've made a comment in MIRTH-4195 that might be relevant.

Imported Comment. Original Details:
Author: [email protected]
Created: 2020-05-01T07:30:43.000-0700

[MichaelLeeHobbs]

Bumping: Can we please have this fixed?

[jonbartels]

Related issues and discussions:
#5284
#4072 (originally MIRTH-4195)
#4206

[ppazos]

Any updates? I have bumped into this in the new Mirth 4.x and opened #5284

[rogin]

I'd like to bump this one as well.

[jonbartels]

@ppazos and @rogin - NextGen has said they are handling gitHub issues based on the number of "thumbs up" votes on the issue. Make sure you upvote it to move this case higher in their triage queue

[rogin]

I created a wireframe from the requirements across the related tickets to understand what all users are wanting. The wireframe is specifically for the dialog popup when a user clicks to clone a channel. I'd like to tackle this ticket, so feedback is appreciated.