Why is the RTC REST API returning the wrong modified date on my work item?
![]() I am using the RTC 6.0.2 REST API to return itemHistory records, but I've run across one work item where the modified dates don't correspond to what is shown in the "History" tab on the UI. What's more, the itemHistory/modified and itemHistory/dayModified fields are off by a day.
I'm using the following REST QUERY:
https://myserver.com/ccm/rpt/repository/workitem?fields=workitem/workItem%5Bid=43739%20and%20projectArea/name=%27XXXX%20Tools%20Project%20%28Change%20Management%29%27%20and%20target/name=%27Sprint%20-%2003%27%20and%20modified%20%3E%202017-06-14T00:00:00.000-0000%5D/%28id%7Cmodified%7Csummary%7CitemHistory/%28modifiedBy/%7Ccomments/%7Ctarget/%7Cpriority/%7Cstate/name%7C*%29%29
For the most part, the data is spot on with what is shown in the History tab, but I've found this one work item that is off by a day. What could be causing this? Should I open a PMR?
Thanks,
Robert
|
Accepted answer
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Jun 18 '17, 5:09 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Please report this as a bug.
I have heard of a case where the GUI ignores "insignificant" changes, while the reporting system does not.
In the bug report, please identify what changes are being shown by the REST service, but are not being shown in the GUI (or vice versa).
Cheers,
Geoff
Robert Huet selected this answer as the correct answer
Comments I believe I figured it out. Looks like the changes returned by the REST API were to links, and the UI did not have the "Include Link History" option checked. When I checked that option, these changes appeared in the UI.
|
One other answer
![]() Are you sure other records aren't off? Something like this is usually because the server has it's time set differently.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.