Cody J. Hanson

@aaronsteers yeah I put this on the backburner since it's definitely a chore that doesn't have any immediate or short-term user impact. It should definitely have the `Urgency=High` flag removed.

This was actually resolved in https://github.com/meltano/meltano/pull/6971; all SettingsServices now have a `project_settings_service` attribute that's used for this. Closing.

Success criteria should also include being able to copy/move multiple state IDs, or a flag (or maybe just running bare without a state ID argument) to just copy/move _all_ state...

@tayloramurphy -- yes we have [these tests](https://github.com/meltano/meltano/blob/main/tests/meltano/core/test_environment_variables.py) for inheritance. The logic itself is consolidated [in plugin_invoker.py](https://github.com/meltano/meltano/blob/d4860127f063fb1234dbaea72452a1a09221ad27/src/meltano/core/plugin_invoker.py#L333) and is well-commented there. I was able to replicate this locally. I think the...

@aaronsteers it's set globally for the project. Do we need to support per-environment state backend configuration as part of scope for this?

@pnadolny13 This should be resolved now, let me know if you continue to have issues.

@pnadolny13 -- the docs apparently were not in line with the actual feature flag name. [Here](https://github.com/meltano/meltano/pull/6680) is a PR for the docs update. I'll dig in a little more this...