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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
After updating Portfolio to 3.9.0 all issues are showing a warning when the due date is the same as the target end. Is there anyway to fix this? All our planned issues are now shown with a warning...
Steps to recreate:
Even the tooltip suggest to set the due date to before or the same as the target end.
I'm a team leader for Jira for Portfolio Server. Thanks for raising this issue, this looks like a regression in our functionality and I've raised internal issue to fix this problem. Unfortunately I can't commit to a future version when this problem will be resolved.
Regards,
Dave
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have the same issue. The warning remained even I changed the due date to be earlier than the target end date.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If the due date is earlier than the target date than that definitely should show a warning.
The due date should be considered as the date the issue absolutely must be resolved by. You can have a target date that indicates the issue will be resolved before the due date, but if you're targeting to resolve an issue after it's due date then you'd expect a warning.
The issue with the due date with a matching target date resulting in a warning will be resolved in the next release of Portfolio (3.12.0).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you Dave. Your explanation helps me a lot. Great to know about the ETA of the warning issue too.
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.