7. Customizing your plans


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


  1. 1. Installing Portfolio for Jira
  2. 2. Preparing your planning environment
  3. 3. Creating Portfolio plans
  4. 4. Managing your teams
  5. 5. Managing your releases
  6. 6. Working with your plans
  7. 7. Customizing your plans
  8. 8. Sharing your plans


Depending on how your organization is structured, the content on this page is meant for Portfolio for Jira administrators or Portfolio plan owners.

To help you set your teams up for success, we've prepared this getting started guide that discusses how to set up Portfolio for Jira with your existing Jira instance.

The guide discusses the typical end-to-end path that users and administrators may find themselves taking part in when using Portfolio for Jira. You'll also find high-level content on Portfolio concepts, as well as some recommendations and optional steps you can consider, as you flesh out your plan.

Customizing plans

Planning work for multiple teams across multiple projects can be challenging, which is why we recommend that you customize the view or the layout of your plans, so you can focus on only the things that you need to focus on.

We recommend that you jump to one of the following sections, based on the type of plan you're using:

Viewing issues in plans with the improved interface

When planning work, you're likely to be managing multiple issues that span multiple projects. It's easy to lose track of your work at one point or another, when you're across multiple work streams. The roadmap view of your plan lets you see all the work that's relevant to you. With the new experience, you can use the different elements in this view, so you can focus on only the relevant details. See Viewing work for more information.

To narrow down on the work you want to view, you can do the following:

Display issue details

You can choose the issue details that you want to display in your plan. These details may include:

課題のフィルタリング It can be easy to lose focus when you're planning work across multiple projects, releases, teams, and more. By filtering the issues that are displaying in your plan, you can focus your attention on a specific scope of your plan.
Customize view settings You can customize the view settings of your plan, to make it easier for your audience to consume the data in your plan. By customizing the view settings, you can make your timeline display the right information, with the right visuals for you and your audience.

Viewing issues in live plans

  • Use the following filters for the issues in your plan: hierarchy level, projects, releases, teams, issue details (key, summary), statuses, completion date, scheduled range, and themes
  • Configure the following schedule settings: timeline (global or projects), grouping (teams, people, labels, or components), coloring (single color or theme colors), and more
  • Configure whether or not to display the following items on the timeline: empty releases, sprints, dependencies, and issue keys

See Scheduling and timeline and Using the timeline for more details.

範囲You can choose which details to display in the scope table. See Configuring the scope view to know more.


Best practice to considerIn plans with the improved interface...In live plans...
Viewing issues in relevant groupingsYou can group and color issues by their attributes, so you can quickly visualize these issues in relevant patterns. See Customize view settings to know more.You can view issues in relevant groupings by configuring the scheduling settings, or by generating a themes report of your plan.
Set up custom fields to represent strategic objectives or themesYou can color your plan by these custom fields, to easily spot what teams are investing into certain themes. You can also spot when deliverables will be completed under different themes. See Customize view settings to know more.Unfortunately, this is not supported in live plans. As an alternative, you can consider generating a themes report  of your plan to spot trends and patterns in your plan.

最終更新日 2019 年 7 月 10 日


Powered by Confluence and Scroll Viewport.