When setting a datetime field in Rally to the ProcessingTime attribute in orphan management, the time portion of the field is not saved in the datetime field in Rally. Instead it is set to midnight (with the workspace offset)
The exception thrown in the logs is
DEBUG yyyy-MM-DD HH:mm:ss,SSS [-999999999 | Automation | 4 | 27 | {}][(orphan-flows) thread #20 - JmsConsumer[processOrphanQ]] com.go2group.connectall.model.transformer.nextgen.NextGenAdapterModelConverter: Conversion of datetime field failed again due to the error:
java.text.ParseException: Unparseable date: "2025-01-17T21:27:35.386Z"
at java.base/java.text.DateFormat.parse(DateFormat.java:395) ~[?:?]
at com.go2group.connectall.model.transformer.nextgen.NextGenAdapterModelConverter.convertFromModelFormat(NextGenAdapterModelConverter.java:264) ~[Connectors-3.6.0.1.jar!/:3.6.0.1]
WARN yyyy-MM-DD HH:mm:ss,SSS [-999999999 | Automation | 4 | 27 | {}][(orphan-flows) thread #20 - JmsConsumer[processOrphanQ]] com.go2group.connectall.model.transformer.nextgen.NextGenAdapterModelConverter: Perhaps Date field mapped with DateTime field.
And then we see the actual payload sent to Rally is as follows:
DEBUG yyyy-MM-DD HH:mm:ss,SSS [-999999999 | Automation | 4 | 27 | {}][(orphan-flows) thread #20 - JmsConsumer[processOrphanQ]] com.go2group.connectall.adapter.rally.base.helper.RallyAdapterHelper: Returning JSON, {"HierarchicalRequirement": {
"c_Date": "2025-01-16T17:00:00",
"Project": "/project/999999999999"
}}
Steps to Reproduce:
Set up an automation that uses Rally as a destination
Configure the orphan management to update a date field in Rally to the Processing time of the orphan management
Synch a work item from source to Rally
Delete the work item from source
Trigger the orphan management and note the time
Expected Results:
Rally date field is updated to the full date and time
Actual Results:
Rally date field only has the date value and time value is effectively midnight (with workspace timezone offset)
DE165160
This is slated to be fixed in ConnectALL version 3.8