When pulling records from lookback API (LBAPI) and examining the parent field such as Feature it shows an incorrect object ID in comparison to what is being represented in webservices API (WSAPI).
Release : SAAS
Component : AGILE CENTRAL
This can happen if the portfolio item type being referenced is renamed. After a rename, the snapshot service begins recording the new portfolio item type name as a new attribute in LBAPI thereby leaving the data in the previous attribute name stale.
In the example above, the portfolio item type was renamed from Feature to Features, resulting in a new LBAPI attribute called Features which held the correct object ID. Changes like this can break code that relies on the specific portfolio item type name attribute.
Refactor any code to look at the PortfolioItem attribute in the LBAPI response instead of the specific portfolio item type attribute as the PortfolioItem attribute is a static name that will always reference the correct object ID.