Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Start date of plan not getting updated after upgrade to 2.17.1

Cristiano Mariano
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 19, 2018

Hi guys!
We use Jira Software 7.6.0. After upgrading Portfolio from 2.13.3 to 2.17.1, when we hit the Calculate button in a Plan, the start date is not refreshed. One of the issues we are using for investigation has no Earliest start or Target Dates and also no Dependencies. The issue is assigned to a release, but the release has no start date defined. The plan is showing the start date (and start date of first issues) as October 8th, but current date is October 19th. Have you guys seen a similiar issue after upgrading?
Thank you very much!

1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 31, 2018

Hi @Cristiano Mariano,


I'd suggest checking in the release tab if the release start date is set to "as early as possible". You could also check if the issue has a sprint assigned which could be another reason for an issue to show a start date in the past.

Another possibility would be that the issue does not have an estimate and have a target start date assigned.

In a more environmental topic, it could be that the date on the server itself is wrongly configured.


Let me know how it goes.




Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events