Comparison for identical trackers from different projects

[GT_10907124]

Hello Community,

We have two projects in CodeBeamer. The requirements in the first project are identical in many ways to the requirements in the second project.

We need a tool that will take a tracker from the first project and compare it to the same track in the second project, and do the following: Compare the description field of both requirements.

If the same - copy the "Status" field and some Free text fields from the first project to the second project.

If different - set the status field of the other project to "Under Review".

Is this something that Codebeamer can support?  If not, is there an external tool we can work with to fulfill this need? 

Any solution would be welcome 🙂

Thanks!

[GeoffreyClemm]

The approach I recommend for this situation is not to store the similar requirements in a different project, but rather in a different working-set (in 3.1, a different stream) of the same project.   Then you can use the Baseline-Compare operation to do the comparison you are looking for, and use Merge for the merge you are looking for. 

If you decide to take that approach, you will need to create that second working-set and then "update" the second working-set with the contents of the second project (so that the items in the second project appear as a new version of the corresponding items in the first project).

[vnamboodheri]

Hello @GT_10907124,

It looks like you have a responses from a community member. If it helped you solve your question please mark the reply as the Accepted Solution. 
Of course, if you have more to share on your issue, please let the Community know so other community members can continue to help you.

Thanks,
Vivek N.
Community Moderation Team.

[BKampling_SAI]

Hi @GT_10907124 

You might be able to leverage the round tip Excel functionality.

1. Export each tracker; be sure to check "Include description" during the export.

2. Leverage Excel functionality to do the comparison and update the status values based on those findings.

3. Reimport the updated spreadsheet with the new status.

I only recommend this if it is going to be a one-time occurrence. If this is ongoing, I would recommend establishing a relationship between the two trackers and enabling the propagation of suspect flags.

Let me know if you'd like any more details.