XOGing milestones sets finish date previous to start date

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

I am XOGing milestones into a project and I have noticed that the finish date set is prior to the start date. How can this happen?

This is a sample file used:

<NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_project.xsd">
 <Header version="6.0.11" action="write" objectType="project" externalSource="NIKU"/>
 <Projects>
  <Project projectID="myproject" name="myproject">
   <Tasks>
    <Task taskID="mytask" name="testask" status="2" start="2021-07-13T00:00:00" finish="2021-07-13T00:00:00" milestone="true"  outlineLevel="1">
     <Baselines/>
     <CustomInformation>
     </CustomInformation>
    </Task>
   </Tasks>
  </Project>
 </Projects>
</NikuDataBus>

Cause

When manually creating milestones on the UI a timestamp is set for both start and finish dates. Those being by default 8.00 for the start date and 17.00 for the finish date

Finish date timestamps at DB do get stored as the previous day

Resolution

Provide a timestamp to the date fields:

<NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_project.xsd">
 <Header version="6.0.11" action="write" objectType="project" externalSource="NIKU"/>
 <Projects>
  <Project projectID="myproject" name="myproject">
   <Tasks>
    <Task taskID="mytask" name="testask" status="2" start="2021-07-13T08:00:00" finish="2021-07-13T17:00:00" milestone="true"  outlineLevel="1">
     <Baselines/>
     <CustomInformation>
     </CustomInformation>
    </Task>
   </Tasks>
  </Project>
 </Projects>
</NikuDataBus>

Additional Information

'Midnight rule' - Fields impacted (dates show as one day later)