[JENKINS-36879] Jobs lose their job group if the group is renamed

When you rename a job group that is set to "Jobs marked for inclusion", all the jobs that were marked as belonging to that group lose their assigned group.

I think this is because job group membership is stored by name in the config.xml, rather than by a unique ID, so if the name changes the job is set to be a member of a non-existent group.

---
Originally reported by nridgway, imported from: Jobs lose their job group if the group is renamed

• status: Open
  
• priority: Minor
  
• component(s): prioritysorter-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 20251211-071809
  

Raw content of original issue

When you rename a job group that is set to "Jobs marked for inclusion", all the jobs that were marked as belonging to that group lose their assigned group.


I think this is because job group membership is stored by name in the config.xml, rather than by a unique ID, so if the name changes the job is set to be a member of a non-existent group.

environment

```
Server: Debian 3.2.73-2+deb7u3 x86_64

java version "1.7.0_101"

OpenJDK Runtime Environment (IcedTea 2.6.6) (7u101-2.6.6-2~deb7u1)

OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)

Jenkins ver. 2.7.1

Priority Sorter ver 3.4
```

Start by tracing how the priority-sorter-plugin reads and writes job-group membership in config.xml, focusing on the rename path for groups set to “Jobs marked for inclusion.” Reproduce a group rename with marked jobs and verify that the jobs retain their assigned group after the configuration is saved and reloaded.

Written by the indexing model from the issue text.