History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-11253
Type: Bug Bug
Status: Resolved Resolved
Resolution: Duplicate
Priority: Minor Minor
Assignee: Unassigned
Reporter: Michael Blake
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

Date stamp does not compensate for time zone differences

Created: 06/Oct/06 12:56 AM   Updated: 12/Feb/08 09:03 PM
Component/s: Issue Fields
Affects Version/s: 3.6.4 Enterprise
Fix Version/s: None

Time Tracking:
Not Specified

Environment: linux redhat, mysql
Issue Links:
Duplicate
 

Participants: Anton Mazkovoi [Atlassian], Michael Blake and Scott Farquhar [Atlassian]
Since last comment: 12 weeks, 6 days ago
Resolution Date: 12/Feb/08 09:03 PM
Labels:


 Description  « Hide
example: Create a filter with 'Created After'=04/Oct/06 and 'Created Before'=06/Oct06.

I'd expect the system to return issues created on 05/Oct/06, but I get some that are created on 04/0ct/06 -all are within 8 hours of midnight. I assume the server time (Perth) is set for those issues logged in timezones that correlate to Perth time on 05/Oct/06. The system is not compensating for these differences.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Scott Farquhar [Atlassian] - 07/Oct/06 09:55 PM
Michael,

I believe that JIRA uses the system timezone setup for all date searches.

Is that not what you are seeing?

Or are you after User Timezones? (JRA-9)


Michael Blake - 09/Oct/06 03:34 AM
Scott,
The problem is caused by the way Jira interprets times when users in other timezones log issues.

In JRA-9 Nick says that all times are reported in the server's timezone. This must not be true for dates. See my example above.

Given that this issue was logged in 2002, am I to assume that this issue won't be addressed by Atlassian?


Anton Mazkovoi [Atlassian] - 12/Feb/08 09:03 PM
Hi Michael,

We have a lot of new feature and improvement requests (thousands). We are doing our best in trying to implement the most popular ones, as well as the ones that we think will greatly benefit JIRA.

JRA-9 has been open for a long time, and unfortunately given our workload I am not able to provide an implementation date for it. However, we are not plan to discard it either.

For more information on the way new features and improvements are scheduled please see:
http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements

As far as I can see this issue is a duplicate of JRA-9, and therefore I will resolve it. Please let us know if I misunderstanding this issue.

Cheers,
Anton