Adding target dates

You can use target dates to set up baselines for your team to measure over time.
Here are a few other ways to use target dates:

  • Draft and visualize your long term plan using only target dates.
  • Set targets dates for your work to compare with your calculated plan.
  • Set a baseline so you can compare your current plan with the originally planned schedule as you track your plan over time.
    Note that "done issues" won't show up in the schedule view.
  • Define high-level estimates on issues. As you breakdown issues, you can compare your original high-level estimate with the more defined breakdown.

How to draft your work items based on target dates

Drafting will allow you to visualize your long term plan using target dates. Sometimes, you have an idea of the tasks that must be completed and by when they should be finished. You don't have more information than that. In those cases, you can use the target dates to define the targets.

  1. You can define rough time frames for each issue by adding target start and end dates to the work items.
  2. Go to the Scope table >  and check the fields target start date and target end date so the columns displayed in the scope view.
  3. Create the work items that need to to be done.
  4. Set the targets.
  5. Go to the Schedule settings and select Target schedule from the drop-down menu.

  6. Select Calculate.

    Example: Now you can see the work items  PERF-5 New design, PERF-6 Runtime / backend profiling and optimization, and PERF-8 Fronted optimization marked with a light blue color in the Timeline. The target dates ar displayed with a blue line. See the issue name by hovering over and highlight the issue by clicking it.



    How to display unestimated items

    Unestimated issues will show up in the schedule if they have both target start and end set, or if they have a manual version or sprint assignment, and the schedule unestimated items option is turned on.

    If you turn the unestimated item scheduling option off, the target schedule view will still show unestimated issues that have both start and end date defined with the following color:


How to baseline your plan with target dates

Baselining will help you by comparing your current plan with the originally planned schedule.

Follow these steps to calculate a plan that will be your 'baseline plan'.

  1. Go to Scope >  and check the fields target start date and target end date so they are displayed in the scope view columns.
  2.  Create the work items that need to to be done.
  3.  Go to the Schedule settings and select Target schedule from the drop-down menu.



  4.  Set targets > set target dates from calculated.
  5. You baseline plan is visualized by the blue target date lines and it matches with your calculated schedule.

  6. In this image, you can see your current planned items and how they're tracking against the targets that are defined by the target date blue line.
    As you your team progresses in the work items and makes changes to the plan, you can always use the target dates to track against your current plan status, to have an accurate idea of how the project is tracking.


    Example: 
    The issue IOS- 1 App Basics - iOS target start date was the 14th of December but it has been scheduled to start one day after the selected target. Apparently, the issue is estimated to be completed before the target end date. 



    IOS-20 Group booking experience has been scheduled to start after the start target date and will be completed before the estimated target end.



    As you and your team progress in the work items and make changes to the plan, you can always use the target dates to track against your current plan status, to have an accurate idea of how the project is tracking.


Related topics

                      Configuring the scope view

                      Creating and deleting issues

                      Tracking progress and status

                      Re-prioritizing work items

                      Using scope filters

                      Using scope and dependencies

                      Assigning issues to sprints

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport