This blog entry is to provide suggestions to users who are surprised at incorrect / mismatched date attribute (TIMESTAMP) values seen in RQM artifacts while the data is exported from Excel using the RQM Excel Exporter.
In most cases, the excel export will succeed but you might see that the "date attribute" field, is not in accordance with what is exported.
The dateTime (Date/Time which translates to TIMESTAMP) values in Rational Quality Manager artifacts like Test Case, Test Plans and execution artifacts like Test Case Execution Record undergo translation when the data is coming from excel through the "Export to Repository" option in the RQMExcelWordImporter plugin.
A dateTime value passed through the excel sheet should follow a format yyyy-mm-ddThh:mm:ss+/-hh:mm.
More details on the syntax are available at the dateTime XML schema page
RQM Client and RQM Server in same time zone: If the RQM client (where excel is used) and server are on machines in the same time zone? the TIMESTAMP value specified in the sheet is exported into RQM as is.
RQM Client and RQM Server in different time zone: If the RQM client and server are on different machines? the TIMESTAMP value specified in the sheet is converted to the time on the RQM server and used. to avoid this (i.e., to ensure the TIMESTAMP value is as per client time zone) you should use dateTime (TIMESTAMP) string as 2014-06-29T12:00:00+/-hh:mm
For example: 2014-06-29T12:00:00+05:30 provided that the excel exporter is on a machine which is in India (+05:30) time zone.
If the excel exporter is on a machine in a different time zone, replace the timezone string highlighted above with the relevant value.
You can use a Java Applet online like a sample one here to get the timeZone string : http://whatismytimezone.com/
IBM RQMExcelWordImporter wiki page
RQM work-item # 88184 on jazz.net discussing the dateTime format and scenarios where mis-match is seen
- Technote # 1662739