You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Our portal is showing a Due Date that is minus one day from actual Due Date shown on the Service Desk team view.
Portal Due Date (wrong date)
Actual set Due Date from the Edit Issue screen
If anyone has an idea (and fix! :) ) why this is happening, please comment. Thank you community!
This bug was reported to Atlassian in 2021. It has not been assigned. It has status 'Gathering impact'.
Atlassian offered a work-around:
1. include the Due Date in the email sent to the customer once the issue is created
2. add the correct Due Date in comments notifying the customer that the Due Date displays incorrectly in customer's portal (LOL)
3. purchase an add-on
4. add my vote to the above bug so it will attract Atlassian's attention.
Customer portal will show date and time in relation to the customer profile configuration and their time zone selected.
I suggest you to check with customer if their profile is using tha different time zone from your instance
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Patricia Francezi Coming back on this, since it's still an issue, the above screen captures in the initial description of the issue are both from my own browser/login.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.