Duplicating a Grails Run Configuration does not separate environmental variables

1) Create a Grails run configuration; say "development"
2) Give the "development" configuration an environmental variable "NODE=1"
3) Apply and Save the configuration

4) Edit Run Configurations
5) Select the previously created run configuration, and choose to Copy Configuration
6) Change the environmental variable from 1 to another number; apply and save run configuration

7) Edit Run Configurations and review the original "development" run configuration
8) The environmental variable for this run configuration is changed to what the copied run configuration was changed to

This does not seem to happen if a brand new run configuration is created. It appears to only be an issue if you are cloning run configurations and altering them.

---

*Imported from [IDEA-222099](https://youtrack.jetbrains.com/issue/IDEA-222099) · Type: Bug · Votes: 0*
*Comments, attachments, dates and reporter are not part of the export — follow the link above for the full history.*

Start by tracing the Grails run configuration flow through Edit Run Configurations and its Copy Configuration action, focusing on how environmental variables are handled. Reproduce the steps with NODE=1, change the copied value, and verify that the original configuration retains NODE=1.

Written by the indexing model from the issue text.