Future releases and limitations

このページの内容

お困りですか?

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

コミュニティに質問

This page has been written with the assumption that you've already migrated from live plans (any version from 2.0 to 2.27) to plans with the improved interface (version 3.0 and later).

We're working on more features for the improved planning interface, and we'll incrementally release these features. As such, there are limitations to take note of.

We've also removed some functionality from the improved interface, as we believe some features weren't providing the full value that we had envisioned. If required in your plans, you can still use the removed functionality by disabling the improved interface.

Future releases

Here are some of the features we're considering:

1 課題詳細ビュー
  • At the moment, clicking an issue in your plan will open the issue in Jira.
  • We're working on an issue detail view that opens up when you click the issue. This lets you surface additional issue details without having to leave the context of your plan.
2 Visual customization
  • We've already introduced flexible coloring options in the improved interface, to replace the main value of themes in Portfolio for Jira live plans (versions 2.0 to 2.27). See Customizing view settings and Coloring by custom fields for more details.
  • If you have more ideas and suggestions on visual customization, let us know by clicking the give feedback icon in your plan.
3 Dynamic release dates

The concept of dynamic release dates does not apply in plans with the improved interface at the moment. Currently, if you're purely manually scheduling issues, you would not get a value for release dates. Instead, issues would be grouped into specific releases that don't really have an end date. We're still considering how best to support dynamic release dates in the improved interface.

At the moment, to generate a "dynamic" release end date, you'll need to auto-schedule the issues in your plan. Depending on how your auto-schedule settings are configured, Portfolio may generate a date for this.

4 Reporting functionality

Reporting functionality is currently limited in the improved interface. However, we're currently building more working views that can be shared as reports to relevant audiences.

制限事項

Take note of the following limitations:

Compatibility and layout limitations

1 Limited browser compatibility We highly recommend you use Chrome or Firefox as your browser. You can also use Internet Explorer 11 and Safari — we've fixed some issues specific to these browsers in the latest version.
2 Cannot sort columns in plans
  • It's a familiar operation to sort columns, especially since you can do this in the current plans.
  • At the moment, it's not possible to sort columns in 3.0 plans. Though we unfortunately don't have a workaround for this, we are looking into building this in a future release.
3 Cannot reorder columns in plans
  • When working with columns, it's common practice to reorder columns by drag and drop.
  • At the moment, it's not possible to drag and drop columns in the improved interface. See Displaying issue details for the current workaround.

Technical limitations

1

Lead time in dependency details is not an auto-scheduled value

When you're auto-scheduling your plan, note that the  lead time that appears in the dependency details is not an auto-scheduled value.

Sample lead time of a dependency when a plan is auto-scheduled

2

Progress bar not displaying accurate information

In the new releases view, the progress bar of each release displays the number of issues in the release. You can hover on the progress bar, to see the issues grouped by status category.

At the moment, the progress bar only includes the details of the issues that are currently visible in the plan. This means that old releases may not have accurate information. See Managing releases for more details.

3 Team members are now assignees when planning work
  • Though there are team members in the teams view, you now assign issues to assignees, and not team members anymore.
  • You can assign an issue to only one assignee.
4 Individual capacity planning is replaced by team capacity planning
  • In the improved interface, individual capacity planning is replaced by team capacity planning.
  • When auto-scheduling a plan, Portfolio for Jira will consider the total capacity of a team to complete the work being scheduled. Any individual capacity settings will not be considered.
  • For Portfolio to do this, you must directly set team capacity in your plan.
5 Sprint data may not display in the plan
  • This happens when a plan has an issue source that is not a board. Any sprint data that's associated to an issue source that is not a board will not display in the plan at all.
  • A plan having multiple issue source types will have sprint data displayed only for the issues that are sourced from boards. Issues sourced from projects or filters will not display any sprint data in the roadmap.
  • There is no workaround for this. The only way to display sprint data is to use the corresponding boards as issue sources for the plan.
6

Teams and sprints that have been set in Jira may not display in the plan

  • If a team or sprint is assigned in Jira, but these do not exist in Portfolio, then you cannot select this team or sprint in the fields section of your plan.
  • There is no workaround for this. The only way to have such teams and sprints display as options is to add these in your plan itself.
7 Minor change when entering estimates for issues

Previously, you can enter an estimate for an issue, then click the Enter key to move to the issue in the next row.

In the improved interface, you need to:

  1. Enter an estimate for an issue.
  2. Click the tab key on your keyboard. This will move your cursor to the estimate field of the issue in the next row.
  3. Repeat the above steps as needed.

Removed functionality

We've removed the following functionality from the improved interface:

1 ステージとスキル

We've removed stages and skills for the following reasons:

  1. There's low usage of stages and skills across Portfolio for Jira users.
  2. Stages require regular, manual maintenance, while skills require significant work to break down the skill estimates for each issue in a plan.
  3. Usage of stages and skills contradict with the workflows in Jira.
  4. Any data involving stages and skills only exist in a plan. With no way to integrate the data with Jira, this can lead to lack of transparency. This doesn't work with the product direction we're taking moving forward.
2 Scheduling factors

In current 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 improved interface, this section isn't available anymore. If an issue is not scheduled as expected, you can manually reschedule the issue straight away.

3 Shared people settings

Since individual capacity planning is not supported, any configured settings for the following will not apply to plans with the improved interface:

  • Global availability and absences
  • Team availability and exceptions
4 テーマ

Themes are no longer supported in the improved interface. To replace the main value of themes, we've introduced flexible coloring options, particularly for custom fields. See Coloring by custom fields for more details.

If you need any of the removed functionality in your plans, we'd like to understand this better. Let us know via the give feedback button in your plan.

最終更新日 2019 年 7 月 28 日

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

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