Bug 1028890 - Time zone problem when extracting bug using XML RPC API
Summary: Time zone problem when extracting bug using XML RPC API
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Bugzilla
Classification: Community
Component: WebService
Version: 4.4
Hardware: All
OS: All
unspecified
high vote
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-11 07:08 UTC by Yi Chun Chen
Modified: 2013-11-11 10:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-11 10:26:14 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Yi Chun Chen 2013-11-11 07:08:36 UTC 
Hi Bugzilla Team,

When I try to extract bug from https://partner-bugzilla.redhat.com/ using the XML RPC API, I got such results:

Bug 950099:

last_change_time=2013-10-28 06:57:08
creation_time=2013-10-28 06:57:00

Bug 947788:

last_change_time=2013-11-05 12:10:33
creation_time=2013-09-01 07:02:00

But when I open the "XML" link on the webpage, I got these:

Bug 950099:

<delta_ts>2013-10-28 22:57:08 -0400</delta_ts>
<creation_ts>2013-10-28 22:57:00 -0400</creation_ts>

Bug 947788:

<delta_ts>2013-11-05 03:10:33 -0500</delta_ts>
<creation_ts>2013-09-01 23:02:00 -0400</creation_ts>

I am quite confusing about this result, why there are hours gap between the XML data and the data extracted by the Bug.get API?

Is there any bugs hidden?

Please check this, this is somewhat urgent for the Bug bridge job.

Thanks!
Comment 1 Simon Green 2013-11-11 10:26:14 UTC 
(In reply to Yi Chun Chen from comment #0)
> I am quite confusing about this result, why there are hours gap between the
> XML data and the data extracted by the Bug.get API?

RPC calls return time in UTC. Pages in the web UI return the time according to your preference.

> Is there any bugs hidden?

Yes, there are plenty of bugs that you are not able to see. Bug 1 is an example.

  -- simon
Note You need to log in before you can comment on or make changes to this bug.