Scheduling work

このページの内容

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

Now that you've created your plan and added some issues for your team, it's time to start thinking about how best to schedule these issues for your team.

Portfolio for Jira has a scheduler that considers several issue details, to automatically create a sensible timeline of the work that's relevant to you. With the scheduler, it's easier to spot bottlenecks — this gives you a chance to handle these potential problems even before they happen. As handy as the scheduler can be, you don't really see how it works out your schedule. Ultimately, you're only given the resulting schedule.

With experience and product knowledge, let's say that you know that an issue should be scheduled earlier than what has been plotted by the scheduler. To get the issue scheduled the way it should be scheduled, you'd need to experiment around by changing some issue details.

In the new experience, you can now quickly drag and drop the position of an issue in the timeline, to schedule work your way. You’ll no longer have to guess what you should do, to get issue NPE-3 scheduled on 6 November 2018.

When scheduling work for your team, you may need to do any of the following at a given time:

Scheduling issues

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.
2 Set 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 startdate and target end date for the issue. This will create a schedule block 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.
3 Monitor 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.
  • When a plan is optimized, 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 Viewing work for more details.

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 block of an issue to its new schedule.
  • Edit the duration of an issue by dragging one of the sides of the schedule block accordingly.
  • Change the target dates of an issue in the fields section.

Prioritizing issues

To prioritize work for your teams, you can move an issue to a higher or lower row in the scope section. This moves the position of the issue in both the scope and timeline sections.

For instance, in the sample plan below, you can move TIS-119 from issue row #6 to issue row #5. This way, the issues in the plan will have chronological target start dates.

Prioritizing issues in the new planning experience

  • In the scope section, when you move an issue that has child issues, the child issues will move with the parent issue. However, moving an individual child issue will only move that child issue.
  • The ranking of child issues is independent of the ranking of their parent issues. If you rank a parent epic higher, the ranking of its child issues in Jira will stay as is. This is helpful, especially if your teams have ranked their issues in their Jira boards — the child issues will retain their ranking as is.

Optimizing work for your team

Previously, you'd need to use the calculate functionality to interact with the timeline itself. When you do this, Portfolio for Jira would calculate the scheduled start and end dates of the issues, and then create a realistic schedule of these issues. There wouldn't be any visual indicators of what these calculated changes are, and the changes themselves would be directly implemented in the plan.

In the new experience, you can choose to:

  • manually schedule work, by dragging and dropping schedule blocks in the timeline
  • automatically schedule work, by letting Portfolio for Jira optimize your work based on known issue details. The optimized changes will be displayed in purple stripes for your reference — you can choose to accept these changes, and these changes will then be implemented in your plan.

Note that when you're planning work in the new experience, you can do both manual planning and optimized planning — it's not meant to be one method or the other. For example, during the early, high-level planning stages, you can start by manually creating and scheduling issues in your timeline. Later on, when your teams start adding more accurate dates and estimates to their work in Jira, you can then optimize your plan, to see if your high-level dates make sense.

Optimizing a plan

When optimizing a plan, Portfolio for Jira goes through the following scheduling factors, to create a schedule for your team:

  • Sprints assigned to the issues
  • Releases assigned to the issues
  • Target start and target end dates of the issues
  • Estimates provided for the issues
  • Any dependencies that the issues may have
  • The ranking of work items in the scope table
  • Team schedules, e.g. working in either sprint iterations, or in a continuous flow of daily tasks

Sample plan, with issues not optimized yet

To optimize a plan:

  1. Above the timeline section of your plan, click Optimize. This will display a preview of the optimized changes that Portfolio for Jira is suggesting for your plan. 

    Sample plan, with optimized changes

    Note that in the timeline section, the schedule blocks of the optimized items will appear in purple stripes. Similarly, in the fields section, the corresponding issue details will also appear in purple stripes, of a lighter shade.

  2. Review the optimized changes more closely by hovering on each change, to see the current value saved in Portfolio, and the new value that will be saved in both Portfolio and Jira, if the changes are accepted.


    Comparing current values and new values

    In the example above, two (2) values will be optimized, the target start date and target end date. If you accept the optimized changes, the new values will be updated in your plan.
  3. Perform one of the following actions:
    • To save the optimized changes in your plan, click Accept changes. Note that these changes are just saved in your plan, and are not yet saved in Jira. See Saving changes in Jira to know more.
    • To discard the optimized changes, click Cancel. The optimized changes will not be saved in the plan, nor saved in Jira.

トラブルシューティング

While scheduling work for your teams, Portfolio for Jira will warn you if there are any misaligned dates in your plan:

  • If you set dates for issues that conflict with the dates of their corresponding parent or child issues, you'll explicitly get a warning message for it. This makes it easy for you to quickly fix any dates that may have been mistakenly updated.


    Sample warning, when a child issue starts before its parent

  • If you set target dates for an issue that clash with the due dates coming from Jira, you'll need to modify these dates accordingly. 

    Sample warning, when an issue's due date is earlier than its target end date
  • If you're adding an issue to or removing an issue from an active sprint, note that this will affect the scope of the sprint in progress. In the Review changes dialog, a warning will be shown for such changes on hover.


    Sample warning, when an issue is added to an active sprint

  • If the current date at the time you're viewing an issue is already past the target end date of that issue, you'll explicitly get a warning message for it. You'll also be prompted to update either the status of the issue, or its target end date.

    Sample warning, when an issue's target end date is past the current day's date

最終更新日 2019 年 3 月 12 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.