Ability to relabel base Activity date fields (Activity Begin Date/End Date/Project Anchor Date) (VSTS 149448)

Carolyn Mccarthy 1 year ago in System Administration updated 2 months ago 3

The ability to relabel the base Activity date fields would potentially allow us to remove additional date EAs that we have created and improve user experience by eliminating our request for the entry of duplicate dates. This terminology request would be similar to what has already been done for the base “Administrator” field, which we have renamed to Activity Manager. A Business Case example is today, we ask users to input the same date for the base Activity End Date and the Activity Extended Attribute we’ve created called Out of Market Date. If we could relabel End Date to Out of Market Date, we could potentially remove the need for the separate Out of Market Date EA.

Fields / Attributes

Any update on this?  This is not as salient for us anymore as we hid these fields.