Comments with current date and time

Hi everyone,

I dont know if this is an error, but when we open an artifact, the comments appears with current date and time. It causes confusion to users because they want to see the exact date of these comments.

Thanks in advance

Which version of RRC are you using?

I tried this in both RRC 3.0.1 and RRC 3.0.1.1 M1 and it is showing the artifact comments, in the sidebar, with the date or time they were created - if the comment was created less than a day ago - it shows things like "x minutes ago" or"x hours ago"

Hi everyone,

I dont know if this is an error, but when we open an artifact, the comments appears with current date and time. It causes confusion to users because they want to see the exact date of these comments.

Thanks in advance

Which version of RRC are you using?

I tried this in both RRC 3.0.1 and RRC 3.0.1.1 M1 and it is showing the artifact comments, in the sidebar, with the date or time they were created - if the comment was created less than a day ago - it shows things like "x minutes ago" or"x hours ago"

Hi Robin,

Thanks for answer. I have 2.0.0.4 on server and 2.0.0.3 and 2.0.0.4 on clients.

Hi Robin,

Thanks for answer. I have 2.0.0.4 on server and 2.0.0.3 and 2.0.0.4 on clients.

Hmmm, I can't seem to recreate this on 2.x either.
I have a 2.0.0.4 client and server with comments showing dates back in April and May. I also created some new comments and they too are showing the proper time of when the comment was actually created.

I ran these tests from the rich (eclipse-based) client. The date and time appeared correctly both in the sidebar of the artifact editor and in the Recent Comments feed in the project home page.

Is there anything more you can tell us about your client(s) and server to help try to isolate why this might be happening to you? For example, what timezone setting they might be using. It almost sounds like maybe it's having trouble decoding the timestamp and just defaulting to the current date and time. If this occurs with the web client, we'd probably need to check the server side logs for any anomalies. If this is occurring in the rich client, you can check the client side log file to see if any exceptions occurred (but that might be a long shot). The client log file is typically located here:

C:\Documents and Settings\{Windows login id}\IBM\RequirementsComposer\workspace\.metadata\.log