Scheduling issues

このページの内容

お困りですか?

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

コミュニティに質問

You can schedule issues by setting the duration of issues directly in your timeline, or by setting target dates for the issues. 

  1. Schedule bar of an issue, which you can use to schedule duration of work
  2. Empty target dates of an issue, which you can set to schedule duration of work

Setting the duration of 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.
  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.

    You need the  Portfolio for Jira user permission to save changes in Jira.

The default duration for issues will depend on the timeframe in which you're viewing the plan:

  1. 3M: 1 week
  2. 1Y: 1 month
  3. Fit: The default duration depends on the date range of the issues in the timeline, which affects the width of the issues in the timeline as well. If the width fit is small, then the default duration could perhaps be a week or a month.
  4. 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.

Setting targets dates for 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.

    You need the  Portfolio for Jira user permission to save changes in Jira.

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

Scheduling child issues

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.

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.

Scrum teams work in sprints (or iterations), and they release incremental features of their product at the end of each sprint. When a team and a sprint are set for an issue, you can configure a plan to use sprint dates as the target dates of issues that don't have any dates set yet.

Sample plan with target dates of issues aligning with sprint dates

Even if an issue is showing its sprint dates, you can still change its target dates if needed. Note that if the target dates no longer match the sprint dates, this will not change the sprint assignment of the issue.

When using projects or filters as issue sources

If a plan is using projects or filters as issue sources, sprint data will still be displayed for the corresponding issues.

However, since sprint data can only be directly associated with boards, then the sprints will be displaying the EXTERNAL SPRINT lozenge right next to them. The lozenge is used to indicate that the sprints are not directly associated with the project and filter issue sources.

Sample plan with issues assigned to external sprints

Note the following details about the sample plan:

  1. This plan was created with the project issue source iOS App.
  2. In Jira, the iOS App project has the Scrum board IOS App. In that board, the Koala sprint is currently active, and is running for 2 weeks, starting from 23 June 2019.

When you create a plan using the project iOS App as its issue source, the following will happen:

  1. Portfolio for Jira is not readily able to associate any sprint data to the issues that will be included in the plan. The issues to be included in the plan will come from the iOS App project.
  2. Since Portfolio is not able to associate any sprint data, it will create a plan-specific team known as iOS App (IOS) Team. This means that this team is only local to the created plan. This is precisely why you'll see the issues being assigned to an external team as well, the IOS app Team.
  3. Also because of #1, Portfolio will also display the Koala sprint is an external sprint for the corresponding issues.
  4. In the plan, you can reassign the sprint value, even for external sprints. However, any external sprint will not be available as an option, when choosing sprint values.

Because of this, we highly recommend that you use boards as issue sources for your plan. This will allow Portfolio for Jira to associate any sprint data to the issues in the plan, and the sprints will no longer be displayed as external ones.

Sample plan with issues no longer assigned to external sprints

However, Portfolio for Jira will still go ahead and create the plan-specific team known as iOS App (IOS) Team, which is why the issues in the sample plan above are still assigned to an external team.

You can consider the following options:

Option 1: Add the external IOS app Team to your plan

You can do this by adding the team as a shared team. Note that the external team must already be defined as a shared team in Portfolio for Jira.

IOS app Team has been added to the plan as a shared team

You'll also need to associate the newly added shared team to the corresponding issue source, so the sprint and capacity data will display in the timeline.

Option 2: Assign the issues to the plan-specific team iOS App (IOS) Team

You can assign the corresponding issues in bulk, to the plan-specific team iOS App (IOS) Team. By doing this, the issues will be assigned to a plan-specific team, and no longer an external one.

Issues reassigned in bulk to the plan-specific team iOS App (IOS) Team

You'll also need to associate the plan-specific team to the corresponding issue source, so the sprint and capacity data will display in the timeline.

トラブルシューティング

There may be times when sprint data can't be accurately or completely loaded into a plan, and this can be due to several factors.

The issue may be assigned to a sprint that's not in the plan

The issue may be included in the plan because the project that it belongs to is one of the project issue sources of the plan. If this is the case, then the sprint value for the issue in the plan will be assigned to sprint not in plan.

Ideally, the issue source should be the Scrum board in which that external sprint was created. This way, sprint data can be reflected accurately in the plan.

The same sprint may be appearing in more than one Scrum board

Depending on the number of sprints on each board, the common sprint could have different dates on the timeline. This only happens for future sprints, since sprints are not given any dates until they become active.

For example, we have 2 boards, Board 1 and Board A, and we have Common sprint appearing on both boards. Both boards have Scrum teams associated with them, and these teams work on 2-week iterations. Both teams also have an active sprint.

Both boards have the following future sprints:

  • Board 1: Sprint 2, Sprint 3, Common sprint, and Sprint 4
  • Board A: Sprint B, Common sprint, Sprint C, and Sprint D

With the above conditions, when you group issues by team and show capacity on the timeline, Common sprint will be occurring at different times in each team swimlane:

  • For Board 1, 4 weeks after the active sprint is completed, since there are 2 sprints before it
  • For Board 2, 2 weeks after the active sprint is completed, since there's only 1 sprint before it

This inconsistency will just happen while Common sprint is a future sprint. Once it becomes an active sprint, the dates will resolve themselves across the team groupings on the timeline.

Read on for more details...
  • In Jira, you cannot configure dates for future sprints. A future sprint gets its dates only when it is started, which essentially means sprints don't get any dates until these become active sprints.
  • You can only control the order of future sprints, i.e. in which order feature sprints should be lined up in your Jira board.
  • Portfolio for Jira will try to infer when future sprints will start in the timeline, based on the configured iteration lengths of each team, and the list of sprints for that team's board. Because of this, Common sprint will appear with different dates on the timeline, for both boards.

Two teams share the same sprints, but the teams have different iteration lengths configured

This is related to having the same sprint appear in more than one Scrum board. The only difference is that the iteration length configured for the teams is inconsistent.

For example, you have 2 teams, Team 1 and Team 2, and they're both working on Common sprint in their respective Jira boards, and both boards also have an active sprint.

The teams work in the following conditions:

  • Team 1 works in 2-week sprints in this sequence: Sprint 2, Common sprint, Sprint 3
  • Team 2 works in 4-week sprints in this sequence: Sprint A, Common sprint, Sprint B

Even if Common sprint is the 2nd sprint in the sequence for both team boards...

  • For team 1, Common sprint will be given a 2-week length.
  • For team 2, Common sprint will be given a 4-week length.

その他の注意事項

  • In the improved interface, Coordinated Universal Time (UTC) is always used when handling the dates of issues. This is different from Portfolio for Jira live plans, which use system-enabled dates.
  • Depending on how dates are configured in Jira, the dates may sometimes vary across Portfolio for Jira and Jira. This means that an issue's dates in Portfolio for Jira may be different from its dates in Jira.
  • It's important to note that the change in ranking behavior can produce different scheduling results between live plans (any version from 2.0 to 2.27) and plans with the improved interface (version 3.0 and later). For example, even if issues are placed in the same order across both types of plans, the resulting scheduling results between these types of plans will be different.

     See Prioritizing issues to know more.
最終更新日 2019 年 8 月 21 日

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

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