Scheduling issues

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Scheduling issues is as easy as adding the duration for issues directly in your timeline. Alternatively, you can add target dates for the issues, and these dates will display in the timeline section accordingly.

1

Set the duration of work for an issue

  1. In the timeline section, find the row of the issue you're setting the duration for.
  2. Hover on the row until the + icon and duration for the issue appears.
  3. Click the row to add in the duration for the issue.
    (info) Note that the default duration for issues would depend on the timeframe in which you're viewing the plan:
    • 3M: 1 week
    • 1Y: 1 month
    • Fit: The default duration depends on the date range of the issues in the timeline, which in effect, affects the width of the issues in the timeline. If the width fit is small, then the default duration could perhaps be a week or a month.
    • Custom: The default duration depends on the duration that you set between the start and end dates. If you set a short period of time, then the default duration would be shorter as well.
  4. Save the changes by doing the following:
    1. Click Review changes. The 'Review changes' dialog will display, with all changes selected by default.
    2. Make sure the checkboxes for the necessary changes are selected, then click Save selected changes in Jira.
2Set the target dates of an issue
  1. In the scope section, find the issue that you're setting target dates for.
  2. Set the target start date and target end date for the issue. This will create a schedule bar for the issue in the timeline section.
  3. Save the changes by doing the following:
    1. Click Review changes. The 'Review changes' dialog will display, with all changes selected by default.
    2. Make sure the checkboxes for the necessary changes are selected, then click Save selected changes in Jira.

To quickly remove a date for an issue, click the x icon next to the date.

3Monitor the status of releases

While scheduling work for your team, we recommend you keep track of the status of the releases in your plan.

Click one of the release icons in the timeline section, to view more details about the release.

Sample release icons and details

  • The icons stay green while the release is on track. At any time a release becomes off track, the icon turns red.
  • You can click on the left and right arrows at the top of the release details, to jump from one release to another.
  • When a plan is auto-scheduled, a release that's off track will also display by how much time it's off track. Make sure to check the details of off track releases so you can fix this accordingly.
  • When you're filtering the issues in your plan using releases, the release icons in your plan will also be filtered. See Filtering issues for more details.

You can also use the releases view to monitor all the releases in your plan.

  • In the new experience, Coordinated Universal Time (UTC) is always used when handling the dates of issues. Depending on how dates are configured in Jira, the dates may sometimes vary across Portfolio for Jira and Jira.
  • When scheduling child issues, the start dates and end dates of these issues roll up to the dates of their parent issues. Effectively, this means:
    • the start date of a parent issue would be the earliest start date of all its child issues,
    • and the end date would be the latest end date of all its child issues.

Rescheduling issues

To reschedule issues, do one of the following actions:

  • Drag and drop the schedule bar of an issue to its new schedule.
  • Edit the duration of an issue by dragging one of the sides of the schedule bar accordingly.
  • Change the target dates of an issue in the fields section.

Scheduling issues according to sprints

Before you begin, note that this only applies to issues sourced from Scrum boards and when issues are assigned to Scrum teams.

When a team and a sprint are set for an issue, the target start and end dates of that issue are automatically derived from the assigned sprint.

Sample plan, with target dates of issue aligning with sprint dates

With the sprint set for the issue, you cannot change the target dates for that issue — you cannot drag and drop, nor resize the schedule bar of the issue.

Last modified on Apr 4, 2019

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.