set actual end date of project tasks to current date/time

Prabhh
Kilo Guru

Hello,

We are facing an issue with the Project Actual end dates. On completing a project task, Actual end date of the project task populates to the same as planned end date of that project task. As Project actual dates are based on project task actual dates, if we completes a project prior to planned end date, actual end date populates to the same as Planned end date whereas it should be populated to current date/time for a project as well as all open project tasks.

Kindly let me know how to fix it.

Thank you.

- Prabhh

 

4 REPLIES 4

dave_edgar
Mega Guru
Firstly I’d advise to watch the field to see whats ameding the field so you know what to turn off/amend. And use the code like current. = gs.now(); Hope that helps

leslieh
Tera Contributor

Hi Prabhh,

I'm having the same issue as you with project tasks.  We've upgrading to London and suddenly my Actual Start and Actual End Dates default to the Planned dates.  I found the "Derive time component from planned end dates" field on the project table, but still when set to False the project task is behaving as if it's set to True. 

Anyone else having this issue, or resolution?

Below is from Create a Project Task from a project

Actual start dateDate that the project task began. The task is set to Work in Progress when the actual start date is populated.

When you change the State or Percent complete of the task, the actual dates are auto-populated with time component copied from the planned dates.

When you populate the actual start and end dates, the time component in actual dates is defaulted to the time component in planned dates when the Derive time component from planned dates field on Project form is set to True.

Akhilesh6
ServiceNow Employee
ServiceNow Employee

This is a change in London which has been documented in London Release Notes.

  • The planned start date is copied over to actual start date when the state of a project task changes to Work in Progress. And the planned end date is copied over to actual end date when the state of the task changes to Closed. The actual dates previously defaulted to the date and time when the state change happened.

https://docs.servicenow.com/bundle/london-release-notes/page/release-notes/business-management/project-portfolio-management-rn.html

 

leslieh
Tera Contributor

Thank you Akhilesh - but what then is the purpose of the "Derive time component from planned dates" field if not to stop this action from occurring (by setting it to false)?