PM80909: Sync does not prevent task release conflict when started from parent project

Rational Synergy Interim Fix 1 for 7.1.0.7
Rational Synergy Interim Fix 3 for 7.1.0.7
Rational Synergy Interim Fix 4 for 7.1.0.7
Rational Synergy Interim Fix 5 for 7.1.0.7

APAR status

• Closed as program error.

Error description

• Steps to reproduce:
  
  1) Create a project hierarchy with different releases for each
  project, for example:
  
  TOP-1 (release A/1.0)
   SUB-1 (release B/2.0)
  
  2) Create a new current task with the same release as the top
  level project in the hierarchy (A/1.0).
  
  3) Outside Synergy, create a new uncontrolled file in the work
  area of the subproject (newfile.c in work area of SUB-1)
  
  4) Sync the top level project with the option 'Members and
  Subprojects'
  
  5) Choose to keep the work area change (newfile.c) in the
  resulting conflicts dialog.
  
  - The new file is created in the subproject and associated to
  the current task.
  
  - No warning is displayed that you are associating the new
  object version with a task which doesn't match the release of
  the subproject to which it is being added.
  
  - Therefore the user is not warned that this new object version
  will not be a candidate for Update by default.
  
  If you run the Sync on the subproject icon in the hierarchy, a
  warning *is* displayed when keeping the work area change:
  
  'Release of current task and project do not match'
  
  However Synergy should display the warning message even if the
  sync is performed from a project version which does match the
  release of the current task if the project version being updated
  by the sync does not match the release of that current task.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Sync does not prevent task release conflict when started
  from parent project.
  

Problem conclusion

• Fixed in Ration Synergy 7.1.0.7 iFix001.
  

Temporary fix

Comments

• -NA-
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TLOGIC SYNERGY

• Fixed component ID

  5724V66SN

Applicable component levels

• R710 PSN

     UP