Does not work for servers with negative timezone offset

[rjc570]

Should it work immediately after installation? Do data ware house jobs need to run to pull the data? I am not seeing any errors in the ccm.log file or in the browser developer window. I just get a blank box.

[schneigu]

It should work immidiatly. DW is not involved. Data are from live DB.

[rjc570]

Is there some debugging technique I can use to troubleshoot?

[rjc570]

Should it say "Not Available" in the editor presentation when I am adding it?

I have also checked the deployment logs and it seems it has deployed ok.

[innerjoin]

@rjc570 Thank you for reaching out to us and please excuse my late reply

We have been running the Status History on RTC 6.0.4 for quite a while, the log file excerpt posted by you is looking good and also the setup looks fine to me. It's ok that it says "not available" while adding the presentation (although I would like to know how I can change that label, but that's another story).

One important thing to know is that the status history only shows data if you have saved the work item you are viewing at least once, so I mean that as long as the History tab in RTC does not have any entry, the status history presentation will be a blank box.

To be able to help you to get this up and running, could you check the following:

• One thing that caught my eye is that you seem to be using Mac, so may I ask you what browser are you using? Safari?
• Regarding the debugging technique: Could you open the developer tools of your web browser (typically, this can be done by hitting F12) and check out whether there is an ERROR in the console view?

[innerjoin]

@rjc570 Have you had the chance to look into this again?

[rjc570]

Yes. It is still not working. I have tried it on a colleagues windows computer using different browsers. As well I have tried it with Firefox and Chrome on my Mac. Here are some screenshots.

[innerjoin]

@rjc570 To be honest, I have no clue why this is not working

[mab447]

I'm not sure this is related, but the plugin did not work for us either. It looks to be a locale issue. The modified time, match expression, was using a '+' instead of a '-' for the last 4 digits. When I changed this everything worked as it should. The match filter is in Presentation.js in the createStateHistory function. I used RESTClient to run the GET on the workitem history and see what our date format looked like (which did not have a + in it).

[rjc570]

Where did you find this file, Presentation.js, to change? I did a search in my server directory and could not find it.

[mab447]

It's a file inside the Plugins JAR file.
you'll have to open the jar file in the Plugins folder, make the edit, and update the file in the jar or repackage the jar. Once you open the plugin, you'll find the file in the /resources/ui folder.

[rjc570]

Is this the line you modified?
var exp = /(\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}.\d{3}\+\d{2})(\d{2})/;

[mab447]

yes, for my server the format was:
var exp = /(\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}.\d{3}-\d{2})(\d{2})/;

You should check the format on your server before changing the code, the request in that function is what returns the modified time for each state change in history. (the base URL is https://server:port/ccm/)

[innerjoin]

@mab447 Thank you so much for your help. This seems to be the root cause and I was able to reproduce thiss on my side for servers with a negative time zone offset. I will attach a bugfix and create a new, patched release of it.

[innerjoin]

@rjc570 and @mab447: Please try Version 2.2.5 and let me know if this solves your issue.

[rjc570]

I can confirm version 2.2.5 is working. Thanks for all the efforts.

[innerjoin]

Great, good to hear that :-)