Setting a ConnectALL Rally adapter DateTime field to a Constant value is ignoring the time

Products

• ConnectAll SaaS
• ConnectALL
• ConnectAll On-Prem

Issue/Introduction

Setting a CONSTANT to a datetime value and synchronizing it to a DATETIME datatype field in Rally v2 results in only the date portion being synchronized

 

Logs show the following:

WARN  yyyy-MM-DD HH:mm:ss,SSS [-999999999 | Automation | Automation_9999999999999 | 9999999999999 | {}][(connectall-flows) thread #78 - JmsConsumer[writeQ]] com.go2group.connectall.model.transformer.nextgen.NextGenAdapterModelConverter: Perhaps Date field mapped with DateTime field.

[...]

DEBUG yyyy-MM-DD HH:mm:ss,SSS [-999999999 | Automation | Automation_9999999999999 | 9999999999999 | {}][(connectall-flows) thread #78 - JmsConsumer[writeQ]] com.go2group.connectall.adapter.rally.base.helper.RallyAdapterHelper: Returning JSON, {"Defect": {

  "c_Date": "2030-06-16T18:00:00",

  "Name": "Test reference field sync"

}}

 

Steps to Reproduce: 

1. Set up an automation to Rally (In this case the use case is Rally <--> Rally , but using two different workspaces)

2. Map the Name field

3. Map a CONSTANT to a datetime field in Rally

   1. Set the value to something like 2030-06-17T12:34:56.000Z

4. Create a new work item

5. Run the synch

Expected Results: 

• Destination Rally system gets the datetime field set to the value in the CONSTANT (this should have a timezone adjustment for the workspace timezone setting)

Actual Results:

• Datetime field is set to midnight (again compensated for timezone, but clearly not with the time set in the CONSTANT)

Cause

DE162993

Resolution

This is slated to be fixed in ConnectALL version 3.8