How to merge sets and change the Set Key without renumbering all of the items in the set

Author: Erik Haake

Date: 6/26/25

Audience: Everyone

Environmental details: Cloud and Self-Hosted

Summary

Changing the set key of items is a useful feature which enables a number of different workflows with Jama Connect. Currently, the process for changing the set key of a set of items requires re-numbering all of the items in the set. This can be an issue for some workflows. 

For example, if items from one set are added to another and the set key of the items in the destination needs to be changed, selecting the set and choosing "Change Set Key" will bring up the following dialog:

Without selecting "Regenerate Item Ids", only the set key of the set itself and any future items created within the set will be changed. It will not apply to any of the items currently in the set.

In order to apply the change to the items in the set, the "Regenerate Item Ids" option needs to be checked, however this will re-number all of the items in the set. This is not always desired, for example if there are external references to the items that need to be maintained.

Solution

By creating a set exclusively to change the set keys of items, you can change the set keys of certain items without re-numbering all of the items in the set. Again, this is useful if you are trying to merge a set of items where the set key of one group needs to be changed to match that of an existing group, but you don't want to re-number the items in the existing group.

The steps are as follows:

1. Create an empty set of items of the same type as the items you would like to change the set keys of. This set is only for regenerating the IDs.
   
   
    
2. Move the items you would like to change into this set.
   
   
    
3. Change the Set Key of that set and Regenerate Item IDs.
   
   
    
4. Move those items into their destination set.
   
   

Additional Information/Metadata

• Change Set Key
• Re-numbering items
• Workaround

References

• Change a set key
• Many thanks to Patrick Knowles for providing this workaround.

Please feel free to leave feedback in the comments below.