Changes in the new experience

このページの内容

お困りですか?

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

コミュニティに質問

The following table lists the important changes to note when planning in the new experience.

タスク変更
プランの設定

In the new experience, you can currently configure the estimation, issue sources, and permissions being used in a plan. See Configuring plans for more details.

The following settings the previous planning experience are also used as default:

  • 作業時間と作業日
    • 地域: システムの既定
    • 作業日: 8 時間
    • 勤務日: 月曜日から金曜日
  • シナリオ
    • We're still working on supporting multiple scenarios. See Future releases and limitations to know more.
    • As a default, in the case where an existing plan has been converted to the new plan, the current scenario before the conversion happened will be used in the new plan. There's no way to switch to any alternative scenarios that may have been set up before the conversion.
  • Commit issue assignee: In the new experience, you now assign issues to assignees, and not team members anymore. With this behavior by default, this option is no longer needed in the new experience.
プランの課題を表示する

従来は、以下に示すプランの例のように、課題はプランの上部にあるタイムラインに表示され、チームの作業項目は下部のスコープ テーブルに表示されていました。

In the new experience, you still have the scope table in fairly the same position in the plan, but we now call this the scope section.

However, the timeline has been moved to the right of the scope section, and each issue has its corresponding schedule block. The schedule blocks are displayed in the timeline, according to how these are scheduled, as displayed in the following sample plan.

Visualizing work using grouping and coloring settings

従来はテーマ レポートを使用して、プランに単色かつ単一レベルのビューを適用し、さまざまな作業ストリーム (プロジェクト、チームなど) を個別のスイムレーンに分けることができました。

In the new planning experience, you can now mix and match grouping and coloring options, which let you visually display more details to your audience. This also makes it easier for your audience to consume your plan in greater detail.

Sample plan, with issues grouped by project, and issues colored by status

詳細については、「表示設定のカスタマイズ」をご覧ください。

タイムラインで依存関係を表示する

Previously, you would know if an issue has a dependency if the issue has a light blue bar in either end in the timeline. These visual indicators are not obvious, and are not intuitive to use.

依存関係を持つ課題を含むプランの例

In the new experience, we're making it easier to for you to keep track of any dependencies in your plan. All you have to do is add the dependencies column to your plan, and you can view the existing dependencies straight away. Not only that — you can also create dependencies to and remove dependencies from any issue, directly in your plan.

依存関係を持つ課題を含むプランの例

See Managing dependencies for more information.

課題の作成

以前は、課題を作成する方法は数通りありましたが、そのうちいくつかはユーザーにとって明確なものではありませんでした。

In the new experience, we're redesigning how you can create issues, making these more obvious and more intuitive:

  • 課題はスコープ セクションの上部で作成できます。その際、課題の階層レベルや、課題を関連付けるプロジェクトを指定できます。
  • また、任意の階層レベルの課題にマウス カーソルを合わせて、その課題の子課題を作成することもできます。新しい課題は、同じプロジェクトを既定で継承します。

See Planning work for more details.

課題を割り当てる

In Portfolio for Jira, plans use the concept of team members, which are independent from assignees in Jira. You'd first assign an issue to a team member in Portfolio for Jira, and when you commit this change to Jira, the issue is then assigned to the corresponding assignee in Jira.

In the new experience, we're simplifying this task by letting you set the assignee directly in your plan. This effectively removes that extra step of assigning the issue to a team member first, then saving the change in Jira as an assignee change. One thing to note, in the new experience, you can assign an issue to only one assignee.

課題のスケジュール

Previously, you'd need to use the calculate functionality, to interact with the timeline itself. When you calculate your plan, Portfolio would calculate the realistic scheduled start and end dates of the issues, and then create a realistic schedule of the issues.

In the new experience, we're simplifying the experience by using only one type of date — target dates. You can also directly interact with the timeline itself to schedule issues. You can manually drag and drop issues in the timeline, according to how you want to schedule these issues.

You can also choose to make Portfolio optimize your plan for you and create a schedule of your work. But it's up to you to decide whether or not you'll accept the optimized changes made by Portfolio.

詳細については、「作業のスケジュール」をご覧ください。

In today's Portfolio's plans, you can use the scheduling factors section, to understand how issues are scheduled off your backlog, as well as why some issues aren't scheduled as expected.

In the new experience, this section isn't available anymore. If an issue is not scheduled as expected, you can manually reschedule the issue straight away.

課題のランク付け

以前は、子課題のあるエピックを高くランク付けすると、その子課題のランキングも高くなりました。これらの変更を Jira でコミットすると、Jira の子課題も上位にランキングされました。

特にチームのバックログまたはアクティブ スプリントで課題のランク付けがすでに行われている場合、こうして子課題のランクが突然上がると、混乱を招くことがあります。

In the new experience, the ranking of child issues is now 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.

進捗を計算する

Previously, progress would be calculated by the percentage of the estimates completed against the total estimates.

In the new experience, we now display progress more visually — in a status breakdown bar, which displays issues grouped by status category:

  • blue, for issues that are still in the To do status category
  • yellow, for issues in the In progress status category
  • green, for issues in the Done status category

Jira で変更を保存する

  • Any changes you make in your plans will not be saved in Jira, until you're comfortable with the changes made. These include the manual changes you make in your plan, and the optimized changes that you may have accepted.
  • どの変更を Jira に保存するかは、確認して選択できます。詳細については、「Jira で変更を保存する」を参照してください。
Zooming in and out of the work in your timeline

In the new experience, you can quickly see issues for a set timeframe, like 3 months, 1 year, or a custom date range. This lets you focus on only the issues scheduled within the selected timeframe.

You could also do this in today's plans; however, you'd need to use the scheduled range filter — and this method wasn't too obvious to use.

チームの管理

Previously, you'd manage your teams by clicking the Teams view, at the top-right area of your plan.

In the new experience, team management is accessed via the teams tab above the scope table.

キャパシティの管理

従来は、チーム メンバーの個々のキャパシティを計画することができました。

In the new experience, we're still considering how capacity is best managed. We're starting with the following details:

  • Individual capacity planning is replaced by team capacity planning.
  • When optimizing a plan, Portfolio for Jira will consider the total capacity of a team to complete the work being scheduled.
  • For Portfolio for Jira to do this, you must directly set team capacity in your plan.
リリースを管理する

Previously, you'd manage your releases by clicking the Releases view, at the top-right section of your plan.

In the new experience, release management is accessed via the releases tab above the scope table. We're still iterating on how releases are managed, and this is why the dynamic optimized dates of releases won't be visible as of yet.

作業をレポートする

Previously, you could share details about your plan using different report types, like the capacity report and dependencies report, via the Reports view.

In the new experience, we've removed the Reports view because we're currently building more working views that can be shared as reports to relevant audiences. Although the reporting functionality is currently limited, you can still share a read-only version of your roadmap.

最終更新日: 2018 年 12 月 14 日

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

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