How are the Epic and Project fields display value being defined on a Demand record?

[JeremyHoffman]

Hello! 

I am investigating to figure out how the display values of the scrum_epic and project fields on a Demand record are being set to display the name (short_description) of the respective record instead of the number. I have probably overlooked something in my investigation as I have looked at the Dictionary overrides for Display value on the Demand, Epic, and Project tables, looked at the UI Action for Create Project, and Create Epic, looked at the Script includes, Business rules, UI Policies (and UI Policy Actions), and Client scripts to no avail. While there is a Dictionary override for the short_description field to set it as the display value, when removing that flag, newly created Epics from Demands still display the short_description in the scrum_epic field. 
The issue we are having is the fact that the short_description for Projects and Epics are the same as the Demand's short_description, which is fine, but makes it redundant and useless to display on the Demand record, per our Stakeholders.

Any help in figuring this out would be greatly appreciated.

Kind regards,

Jeremy

[JeremyHoffman]

Update to this...As I was updating my question with more detailed information, I realized that I did not look at the Dictionary overrides for the Epic table (rm_epic.config) and the Project table (pm_project.config). They each have a Dictionary override for the short_description field where the Override display value == true.