After running a custom script which modifies Change Requests (CR), the CR numbers have increased.

0 Likes

Problem:

After running a custom script which modifies Change Requests (CR), the CR numbers have increased.

Resolution:

* Product Name: StarTeam
* Product Version: 2006, 2008
* Product Component: Client
* Platform/OS Version: All


Description

Change Request (CR) numbers have ‘jumped’ or increased after running a script.


Answer/Solution

Shared CRs that are modified and therefore branch are causing this ‘jump’ or increase in the CR numbers.

For example, suppose the last CR created has a CR number = 100. After running a custom script which modifies CRs, you notice the next new CR number is 110. This means 9 CRs have branched.
The reason behind this is in the database. A CR number is calculated by the maxObjectID 1. If a CR branches it creates a new row in the database. This new row, has a new ObjectID. Due to the change in the ObjectID the next new CR created will have an inflated change request number.

This is by design, and if you see a large change in CR numbers, this is most likely down to a large number of CR’s branching via the script.

As a test you can confirm this behavior via the CPC.
1 - Create a new CR (for this example assume the new CR number = 100).
2 – Share the CR to another folder.
3 – Now modify the CR that was just shared in the new location, so that it branches.
4 – Create a new CR.
Notice the CR number for the CR created in step 4. In this example you would ‘expect’ to see 101 as the next change request number, but in fact it’s 102. This is normal and by design.

Old KB# 29144
Comment List
Related
Recommended