Bug 1418254
| Summary: | search filter with last change date (delta_ts) does not work properly | ||
|---|---|---|---|
| Product: | [Community] Bugzilla | Reporter: | Michal Hlavinka <mhlavink> |
| Component: | Query/Bug List | Assignee: | PnT DevOps Devs <hss-ied-bugs> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | tools-bugs <tools-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.0 | CC: | crobinso, dan, huiwang, qgong, yijli |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-02-14 02:30:40 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Michal Hlavinka
2017-02-01 11:39:34 UTC
The difference between BZ4 and BZ5 appears to be due to a time zone transformation done as part of the upgrade process. If you use EST times for BZ4 it should match the BZ5 behavior using UTC times. "boolean_query" isn't a Bugzilla feature, it's a pyton-bugzilla feature, you should probably chase up that community to see if it's working as expected. (In reply to Jeff Fearn from comment #1) > The difference between BZ4 and BZ5 appears to be due to a time zone > transformation done as part of the upgrade process. If you use EST times for > BZ4 it should match the BZ5 behavior using UTC times. the problem is that the result uses one timezone and query uses different time zone. I'm not picking random time, but I use the time that bugzilla returned. Result and query should use the same time zone without need to do any magick on user side. > "boolean_query" isn't a Bugzilla feature, it's a pyton-bugzilla feature, you > should probably chase up that community to see if it's working as expected. Thanks for the info. I will investigate this more. (In reply to Michal Hlavinka from comment #2) > (In reply to Jeff Fearn from comment #1) > > The difference between BZ4 and BZ5 appears to be due to a time zone > > transformation done as part of the upgrade process. If you use EST times for > > BZ4 it should match the BZ5 behavior using UTC times. > > the problem is that the result uses one timezone and query uses different > time zone. I'm not picking random time, but I use the time that bugzilla > returned. Result and query should use the same time zone without need to do > any magick on user side. Do you have your user preference for "Timezone used to display dates and times" set to "Same as Server"? yes, both in production and beta bugzilla. Btw, my complain is not that the time is shifted compared to time on my computee. I get bug's delta_ts from server (xmlrpc) in some timezone and when I use the same time as parameter, it's wrong from server's p.o.v., because it probably does some timezone conversion only in one direction. Either in get data on server -> send to user OR data form user -> server. It should do such conversion in all cases or never. (In reply to Michal Hlavinka from comment #4) > yes, both in production and beta bugzilla. Btw, my complain is not that the > time is shifted compared to time on my computee. I get bug's delta_ts from > server (xmlrpc) in some timezone and when I use the same time as parameter, > it's wrong from server's p.o.v., because it probably does some timezone > conversion only in one direction. Either in get data on server -> send to > user OR data form user -> server. It should do such conversion in all cases > or never. Yeah I'm just trying to figure out which parts of the code are in play for this. Bugzilla doesn't actually store the time zone in the DB >_< But it looks like BZ5 behaves properly so it may be an upstream fix. OK, so to summarize this bug 1: the time shifting appears to be fixed for BZ5 2: the boolean_query issue appears to be a python-bugzilla bug If this is correct than there is nothing for us to do here. Hey Cole, have you heard anything about boolean_query being funky with times? (In reply to Jeff Fearn from comment #7) > Hey Cole, have you heard anything about boolean_query being funky with times? No, but FYI to the reporter the next version of python-bugzilla is killing the boolean_query logic in favor of converting a web query URL to XMLRPC with helper functions. Details are buried in here: https://lists.fedorahosted.org/archives/list/python-bugzilla@lists.fedorahosted.org/thread/WCYPOKJZFYOW7RRT44FCM5GQU26O56K4/ And API example here: http://blog.wikichoon.com/2014/05/invoking-bugzilla-query-url-from.html (In reply to Jeff Fearn from comment #6) > OK, so to summarize this bug > > 1: the time shifting appears to be fixed for BZ5 > 2: the boolean_query issue appears to be a python-bugzilla bug > > If this is correct than there is nothing for us to do here. I agree, given the plan to switch to BZ5 soon, it probably does not make sense to waste time with bz4 fixes right now. (In reply to Cole Robinson from comment #8) > (In reply to Jeff Fearn from comment #7) > No, but FYI to the reporter the next version of python-bugzilla is killing > the boolean_query logic in favor of converting a web query URL to XMLRPC > with helper functions. I've noticed this in git, so I've change all queries in our tool to use {field,value,type}X-Y-Z format |