From foreman-dev email...
As a side note, editing a SP in the UI in org A properly displays just A's lifecycle environments for inclusion. However, switching to B and modifying the SP w/ B's lifecycle environments effectively erases any that were previously associated from A. (I believe there may be an already existing catch-all bug for this since the same behavior exists (existed?) when edit relationships on the org page itself. (ie. If the user did not have permissions to see all templates, when they saved their choices it would erase any previous assocations.)
Created from redmine issue http://projects.theforeman.org/issues/6587
Moving bugs I'm not currently working on back to NEW.
This is a duplicate of #1103157. The problem here is that you must pass ALL of the IDs or else you unintentionally erase some.
*** This bug has been marked as a duplicate of bug 1103157 ***