|
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Owen Fellows - 16/Nov/03 07:55 PM
This is due to users not having a timezone set, see linked Issue.
You could presumably identify the user's locale from the request too...
I'd like to see this feature aswell. In a centralized server that is shared internationally, people want to see local times not EST or GMT.
This cannot be inferred from the locale in my opinion. I might live in the US and have a timezone of EST but want to display the German language interface. This is very important to us since our users are spread throughout the USA in every timezone. We use date fields to determine the responsiveness (Mean time to respond) to an issue. Not having the local timezone has been causing problems for some users since they get it wrong by up to three hours.
I'd like to see it implemented too. Our users are going crazy with the math
 1) It does not seem to be possible to configure a timezone anywhere
2) At the very least, the time displays should include the timezone being used We're using Jira across about four offices and some time zones for them are 12 hours away. It makes it very confusing to figure out when a change has been made to a bug. I've added my vote.
Yeah this is a key option for users who aren't worldly sensitive to time
Hi,
This doesn't seem to have been answered specifically so: Using Windows XP and IE 6, if I have a TZ environment variable properly set, will JIRA pick that up and report the local time? Thanks. Patrick,
All times are currently reported in the servers timezone. We will post when we schedule user specific timezones. Cheers, Is there any ETA for this feature in JIRA? I've had some requests for this recently.
Thanks, I work in a large global organisation which has recently adopted JIRA. This timezone fix is essential to us as we are scattered across different timezones and tracking when an issue was logged / updated in our own timezone is critical.
It is very disappointing that a simple feature request is now outstanding for over three years!!! I imagine this was overlooked when this product was evaluated and I for one would have seen this as a potential showstopper to purchasing this. There is a bit of debate whether this is hard or easy....
Though Confluence guys just managed to put it into 2.3. so I guess we may revisit soon. We don't really consider how long an issue has been open when scheduling, we try to schedule the most important issues at the time. Sorry I don't have any more info at the moment. Cheers, I would like to add my support for this new feature. It would certainly be advantageous to our users if they could see times in their local time zone, rather than that of the server.
Wow, still open for debate after 3 years? I too work for a company that's got people all over - California, Boston, Belgium, India, ... This is the only tool we use that does not support client-specific timezone adjustment.
You're right Jeff: how something so simple can not be implemented? Even Confluence support it...
Just want to add my two cents that we'd really like this feature. We are a small company with most employees located in California, but we have employees all over the U.S. We just moved our JIRA server to a data center located out of the timezone. I assumed that I'd be able to configure the timezone since I can do that today in Confluence. I was surprised that I couldn't configure the timezone and was disappointed to see this feature request open for almost 3 1/2 years.
Atlassian, I love you guys. I love JIRA and Confluence, but I find myself frustrated at the differences between JIRA and Conflence. It's very frustrating to see a feature available in one product, but not the other. It leaves a strong impression that you treat the two products almost as if they were run by separate companies. Please, please strive to get more consistency between the two products and please, please implement this feature. I think this really should have been in from the beginning. The main reason is not that it allows people from different timezones to collaborate. For me, the main reason is that I believe a server's timezone should always be set to GMT / UTC to shield it from the wackiness of daylight saving time and switching timezone. In this scenario the pure server time is "unusable" for nearly all JIRA users (relatively few people live in a GMT timezone). For instance, we're on Eastern Time in the U.S., but the JIRA time is always GMT.
So, please fix this soon since it makes tracking down times and dates usable in JIRA for us. I actually think that this is a HIGH priority. Without this feature, the only option is to create a separate Jira system for each time zone, which is not a good solution at all.
I really think this feature should have a higher priority. Medium, if not High... but definately not Minor.
This is one of those things that seem minor but cause quite a bit of inconvenience from an end-user perspective. I've just started using JIRA and I am really liking it. I noticed that one of my colleagues had logged an issue at 3:37am, which I am sure she didn't and a bit of digging around revealed that this was a different timezone. We're using an Enterprise Edition of JIRA with projects running across different continents and this feature is an absolute must in order to help us correctly synchronise and track issues. We are also seriously looking at Jira at the moment, and a major blocker for us is the lack of user timezones. We need "follow the sun" support for our support teams and it's critical that the user's local timezones are used.
Has this been scheduled for a future release? Hi,
Thank you for your comments and feedback. We realise that this issue is important and would like to implement it in the future. We have a lot (thousands) of feature and improvement requests and our main challenge is to select which features to add next. We woud like to do this feature carefully as users can exist in various time zaones and every time a date is entered (due date, date and date/time custom fields) we need to ensure we do not store the wrong date. Unfortunately, at the moment this feature is not scheduled for a particular release, and therefore I am unable to provide a date for its implementation. I am sorry for not being able to help more at this time. Thanks, Hi Anton,
It would help others if Atlassian provided an FAQ on scheduling issues. The response below is a nice way of saying that the issue will remain unscheduled and that's the way it is. I believe people want to know one way or the other whether an issue will be fixed. James. What I have now understood is that if you want really want something done in JIRA, there is no other solution than doing it yourself.
Likewise, this is a critical issue for our organization as well.
I have a question... What is the impact of changing the timezone on the live system? What happens to the information currently in the MySQL database? This question is also tracked in https://support.atlassian.com/browse/JSP-16047 It depends on the database and whether there is timezone information in the date columns. Postgres for example stores the data with a timezone, so if I change my JIRA server timezone from GMT+10 (Sydney) to GMT+0 (London) then the display of the time (say on the issue updated time) will go back 10 hours. So if originally I edited it at 5pm Sun, change my JIRA timezone to London then re-display the issue it will show it was updated at 7am.
MySQL timezone support Hi,
The FAQ for the way issues are scheduled can be found here: We are listening, and with every release we try to enhance JIRA as much as we can. Some of the popular requested features included in the last few releases are:
We would prefer to leave this issue open as we are planning to look at it in the future. However, as I have mentioned in my previous comment, we do not have the date for its implementation. Cheers, Jed,
It means you can loose your data consistency only by switching your JIRA installation from a server to another. So it makes crystal clear that you cannot rely on the database to manange timezones and raises this issue criticity. Cheers, Jean-Baptiste Yes, this is also a critical feature for our company, with offices and clients spread around the world. With the newly added/improved work log functionality (good work by the way!) it becomes even more important.
This is also important for us. We have offices in UK, Europe, across North America and Australia and each time zone has to try and convert back to GMT (where the server is based) - it makes thing very difficult.
I am displaying the current server time in the footer. This makes it easier for users to at least quickly judge how old a comment is.
Just edit $JIRAHOME\includes\decorators\footer.jsp old: footer.jsp ...
<div class="footer">
...
new: footer.jsp ... <div class="footer"> Current Server Time: <%= new java.util.Date() %> <br/> ... If someone who knows JSP can tell me how to format the date above into "dd/MMM/yyyy hh:mm a z" format it would be appreciated. We have the same problems mentioned above. We have offices in California and Korea with multiple users collaborating on projects with deadlines that involve users in both places.
In Korea if issues are logged to be completed by April 1st 9am, that would be Mar 31st 5pm here in California. Clearly, this could be problematic if a deadline is misinterpreted. In any event, I'm voting for this issue to be fixed and hopefully included in a release sooner rather than later if at all possible. Thanks, Adam G. Saint-Prix [Outspark] We are implementing globally and need different timezones for each office. We created a separate project for each office. Ideally, it will adjust for the timezone of each user but setting a timezone by project would also be acceptable for us.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Minor
User Preference: User Time Zones
