Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,365,966
Community Members
 
Community Events
168
Community Groups

JIRA Timezone

Edited

My projects timezone is set as GMT-5 which is EST, but whenever my team members are updating stories, the timestamp is getting picked as GMT which is ultimately resulting in wrong metrics being reported.

 

How do we go about this issue?

 

@Rajashree Chandrasekar 

1 answer

0 votes

Hello @Rizwan Ahmed Khan 

Welcome to the community.

You cannot set a time zone per project. You can only set the time zone globally for the Jira instance. 

Users can set a time zone preferences for themselves which will affect the display of the timezone data for them.

Can you provide detailed information on

- the time zone setting for your Jira Instance

- how metrics are being reported incorrectly, including an example of any filter you are using,

- the details for an issue that is included that you think should not be

- the details for an issue that is not include that you think should be

Thanks for your response. To answer your follow up queries :- 

 

Time zone setting of JIRA instance is GMT -5. i.e EST tiemzone

Metrics like velocity are being calculated based on the start time and end time of the sprint. 

 

As I add a story to a specific sprint the timestamp is captured in GMT. But then when i start the sprint considering EST timezone, it implies that the story was added after the sprint was started. Therefore this story gets flagged with '*' mark 

 

I want the timestamps for all the updates made by team members to be in EST rather than GMT. 

Hello @Rizwan Ahmed Khan 

I have attempted to recreate your issue.

I have set my Jira instance default timezone to GMT -8

I have set my account timezone preference to the same.

I add a story to a sprint. When I look at the time stamp information shown in the UI for the update of the issue and the History entry for adding it to the sprint, those are all showing in the GMT -8 time.

When I start the sprint the dialog includes fields for setting the Start date/time and End date/time for the sprint. The default Start date/time is current for my local date time.

Let us say I start the sprint 2 minutes after adding the issue. When I then look at the Sprint report there is NOT an asterisk next to the issue indicating it was added after the start of the sprint.

I made a few time zone adjustments both to the Jira default timezone and my account timezone.

The only way I have been able to recreate your issue where an issue added to the sprint before it is started ends up with an asterisk in the sprint report is if I manually change the time setting for the Start Date/Time of the sprint.

One scenario I was not able to test out yet was when a different user with different time zone settings is either adding the issue to the not-started sprint or starting the sprint, to then see what appears in my view of the Sprint Report. (I am the only user in my test Jira instance.)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS

Atlassian Community Events