-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
4.4.1, 3.16.13, 4.7.1
-
1
-
Severity 3 - Minor
-
3
-
Issue Summary
The SLA in Service Management queues displays the SLA time based on the server time zone, instead of the user preferred time zone – even though the SLA appears correctly on the issue view.
Steps to Reproduce
- Create a JSM request with an SLA
- Change the user profile time zone to differ from the system time zone
- Visit a queue that contains the ticket
- Compare the SLA Due Date on the queue versus the ticket
Expected Results
The Queue displays the SLA Due Date based on the user's preferred time zone.
Actual Results
The Queue displays the SLA Due Date based on the system time zone.
Workaround
View the request on the issue view to assess the correct SLA Due Date for the user's time zone.
- links to
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
We appreciate your time in submitting bugs to our product team and encourage you to continue doing so. Many features and functions in our products come from valued customers such as yourself. You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Service Management Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Service Management Data Center