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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,559,818
Community Members
 
Community Events
185
Community Groups

Difference between Schedule and Target schedule

Can you help me to find the difference between "Schedule" and "Target Schedule" view.

2 comments

The 'Schedule' view is the actual schedule, based on the dates of the sprints you have your cards in.  'Target Schedule' utilizes the optional 'Target Start' and 'Target Due Date' fields on Stories & Epics in Portfolio.  If you use these fields, the 'Target Schedule' view will show you the variance between work was planned (Target Start & End) vs. when it was completed (Actual Start & End).

Like # people like this

How many date inputs are there for Jira? (I'm typing this out for my own sanity for anyone to comment on)

  1. Estimated: this is a range input that's measured against the work log
  2. Planned: these are calendar inputs to determine the time work starts and ends
  3. Target: this is a more specific input created in Jira Portfolio by the assignee
  4. Due: this is an input by the reporter that has a hard deadline
  5. Actual (opened to closed?) I think this input is generated when the issue is placed in progress and is then measured to the close of it.

I sort of see them as levels of intensity.  My experience is that no one really cares about the "estimated", unless the team is really attentive, but then administration maintenance concerns creep into thoughts meant for development / productivity.  This isn't to say "estimated" is bad, just not always used.

"Planned", "Target" and "Due" are the most valuable and "Actual" is a passive input that feeds the burn down charts (?).

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events