Tracking the usage of Original start and end dates for projects

[Jeffrey_K]

We would like to capture the original planned start and end dates before the project begins execution and create a snapshot once the plan is finalized to track delivery metrics through the project life cycle.

There are original start/end date fields in ServiceNow that served this purpose. Unfortunately, as of the Utah release the planned and original dates will always be synced. ServiceNow has said that the original start/end date fields could be deprecated in the future.

One recommendation was to use data from the baseline table, but depending on the project there is a lot of data to sift through and difficult to make usable for leadership in a ServiceNow report.

Any other customers faced with this use case? If so, how are you capturing/tracking that data? What was your solution?

Please respond to this post or DM me if you have any recommendations.

Appreciate any feedback or suggestions.

TIA, Jeff

[Mark Manders]

Most of the clients I worked with didn't really care about that information, so we were never looking at this as being an issue. If it is of importance to you and since it just is for reporting, why not create two custom fields that you set on the first planned start/end date and you can compare it in your reports? And since the fields are custom, ServiceNow will never touch them or deprecate them.