I know we're "behind" a version (we're on-prem), but we're seeing a lot of instances where cloning policies results in a new policy with no packages or scripts... almost like the clone button *removes* those now. I wasn't sure if I should even report this since we'll probably be told to upgrade, but is anyone else seeing this?
For example, I have a policy with a package to install Chrome (very simple example). I click "clone" and get a package with the same name (+ copy at the end) scoped the same way with the same trigger... but no package.
