PM89527: [wi 137331]: The Artifact Container field of project link descriptions does not update when project names change

APAR status

• Closed as Permanent restriction.

Error description

• Steps to reproduce:
  In the web ui, from the project management page:
  Create two projects (Project 1, Project 2)
  Link them to each other
  Change their names (to Project 3, Project 4) and save
  Reopen the project area editor for either project and the
  Artifact Container field will still say Project 1 or Project 2
  But when you click on either link it will take you to the
  correct project area page (with the new name)
  
  The issue can be reproduced with any combination CCM, QM and RM
  projects.
  
  https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.Wo
  rkItem/137331
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Steps to reproduce:
  In the web ui, from the project management page:
  Create two projects (Project 1, Project 2)
  Link them to each other
  Change their names (to Project 3, Project 4) and save
  Reopen the project area editor for either project and the
  Artifact Container field will still say Project 1 or Project
  2
  But when you click on either link it will take you to the
  correct project area page (with the new name)
  

Problem conclusion

• There is currently no technically feasible way to address
  this apar. At best we could make the workaround
  incrementally easier, but it would be considerable work and
  an ugly solution. Read access concerns (project A links to
  project B but we don't know there's a back-link - and the
  user needs access to project B in the first place) and write
  permissions (users need permission to edit the associations
  of any project) make the implementation of a solution
  without security loopholes untenable right now.
  

Temporary fix

Comments

APAR Information

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

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

Fix information

Applicable component levels