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
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.
I am new to JIRA portfolio and am trying to schedule a "Project" . I am just interested in tracking at a high Level(Milestone Based planning) in Days.
I have created a few tasks under the Epic and have set dependencies. The first task's duration is 40 days but I am noticing that the "schedule end date" is not changing .
Task 1 - Estimate = 40 days, Sch. Start = 08/20/18, Sch End = 08/28/18
Expected Behavior :
Task 1 - Estimate = 40 days, Sch. Start = 08/20/18, Sch End = 10/20/18
Appreciate any insights/clues on this behavior.
One possibility here is that the default team working hours is being used to calculate a date indicating that the task can be completed in less time.
So for example your task might take 40 "person-days" but the default team capacity 200 weekly hours (e.g. 25 person days per sprint). One thing you could try is changing the team capacity to be a 40 hour week (you can achieve this by assigning a person to the team).
The Portfolio Team
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.