Tasks are not associated to CRs in Central Server environment
Associating a task to a CR from the Rational Change show form can fail while writing a success message to the CR status log.
In the Rational Change show form, associating a task to a CR does not print a message to the log indicating that an associated_task relationship has been created between the task and the CR. The task is not listed in the associated task list in the form.
This issue can be caused by the task missing its cluster_id attribute. Rational Change Central Server relies on the cluster_id of a task to uniquely identify task objects when performing associations and creating ghost CRs in development databases. The absence of the cluster_id attribute prevents ghost CRs from being created in development databases.
There is no reason for the cluster_id attribute to go missing unless deleted manually.
Rational Change Central Server setup using Change 5.2.x and Synergy: 7.1.x
Resolving the problem
Perform a copy task operation on the problematic task, keeping the same objects associated. Place the original task in the excluded state and complete the new copied task. The new task has a cluster_id attribute. Use DCM to transfer it to other development databases as required.
|Software Development||Rational Synergy||AIX, Linux, Solaris, Windows, HP-UX||7.1a, 126.96.36.199, 188.8.131.52, 7.1, 7.0||All Editions|
More support for:
Software version: 5.0, 5.1, 5.2, 184.108.40.206, 220.127.116.11, 18.104.22.168
Operating system(s): AIX, HP-UX, Linux, Solaris, Windows
Reference #: 1473056
Modified date: 30 October 2012