Jimi is an automation first no-code platform designed and developed originally for Security Orchestration and Response. Since its launch jimi has developed into a fully fledged IT automation platform which effortlessly integrates with your existing tools unlocking the potential for autonomous IT and Security operations.
Is your feature request related to a problem? Please describe.
Instead of Mirror and Duplicate, we should move to a place where you can only mirror objects. Then you can decide to keep them "linked" or "unlinked". This would allow for a more user-friendly situation where you can get a copy of an object and if you want to make it unique you just click the unlink button and it generates a new object ID to be used (keeping the flow ID).
Describe the solution you'd like
Next to the save and close buttons, have a link/unlink button to set the object to mirrored or not. If the user requests for linking they can provide a link ID and then choose whether to inherit the link ID's properties or to overwrite the link ID object.
Additional context
We would need to consider making sure the objects are the same, and checking permissions that the user can read/write both objects.
This would make the copy-paste function nicer too as you would essentially copy a "linked" flow which you could unlink bits of if you required.
Is your feature request related to a problem? Please describe. Instead of Mirror and Duplicate, we should move to a place where you can only mirror objects. Then you can decide to keep them "linked" or "unlinked". This would allow for a more user-friendly situation where you can get a copy of an object and if you want to make it unique you just click the unlink button and it generates a new object ID to be used (keeping the flow ID).
Describe the solution you'd like Next to the save and close buttons, have a link/unlink button to set the object to mirrored or not. If the user requests for linking they can provide a link ID and then choose whether to inherit the link ID's properties or to overwrite the link ID object.
Additional context We would need to consider making sure the objects are the same, and checking permissions that the user can read/write both objects. This would make the copy-paste function nicer too as you would essentially copy a "linked" flow which you could unlink bits of if you required.