How is Planned Start Date and Planned End Date populated on Enhancements?

[tahnalos]

We have recently discovered that SPM auto populates the Planned Start and Planned End date fields for any form that is a child of the rm_feature form.  Because we are using this field on rm_enhancement directly, the system is not allowing us to populate these fields manually.  On the dictionary, the base default value for these fields from Planned task is

javascript:new GlideDateTime().getDisplayValue()

In order for us to use this field on rm_enhancement we have utilized a Dictionary Override to force the Default Value to blank.  We have also done this for User Story and Defect.  However, while the planned dates for User Story and Defect remain blank, the planned dates for Enhancement do not.   We even tried to override this by putting in a business rule on insert that would blank these fields but this also didn't work.  Is there a piece of code that is automatically populating these fields on Enhancement?

[Tanushree Maiti]

Hi @tahnalos 

 rm_enhancement inherits from the parent rm_feature table, OOTB Business Rules, UI Policies, and Dictionary overrides in the SPM application enforce automatic calculation.

To allow manual population of the Planned Start and Planned End date fields on the Enhancement form:

• Check if any oob ui policy on Enhancement table enforcing read-only behavior
• Check if any Dictionary override records that enforce read-only status specifically for Enhancement
• Check if any BR like Display Business Rule called Set Project Task Data  executing on enhancement table ( refer: https://www.servicenow.com/community/spm-forum/planned-start-date-of-project-task-populates-automati...)

[tahnalos]

I am aware that the Enhancement form is an extension of Feature table.  In fact, I already pointed out that the Planned Start Date and Planned End Date fields are from Planned Task and that Enhancement, Feature, Agile Story, and Defect are extensions of Planned Task itself.  The idea that UI Policy and Display Business Rules may have something to do with this is absurd due to the fact that several test enhancement entries were created on the system with MINIMAL DATA as seen below.

Neither a display business rule (for a completely different table, mind you) nor a UI policy would explain why the data is automatically populated, especially since I already pointed out that Agile Story and Defect do not have this issue, only enhancement.