Make Reports' Calculated Fields immune to the Workspace selected when report is executed

Currently, when you create a report (or pivot), the field names in the Calculated fields are based on the workspace selected when the report is run. Even if you provide a user a link to a report and they open it, the system defaults them to the workspace they were last in irrespective of the filters used within the report. If the workspaces the report is filtering on uses a different terminology than the workspace used when the report is run, the formulas fail. This creates a great deal of confusion with the users.

One approach to solve for this is to make the field names used on the formulas be based on the Out of the Box names for the objects and not on the terminology changes. This way, you don't have to update the formulas every time someone changes the workspace they are in when executing the report.

Use Case:

Within, different groups have opted to name Epic differently. The default terminology is "Parent Feature", but many teams have selected "Capabilities" as the name. Depending on which workspace the user is in, the formulas for the report have to be updated to reflect their terminology. That is painful not knowing where everyone is. Furthermore, this doesn't allow you to run reports that cross workspaces with different terminology.