Displaying issue details
You can choose the issue details that you want to display in your plan. These details may include:
- Issue details pulled from Jira (for example, assignees, sprints, and more)
- Custom fields in Portfolio for Jira (for example, target start dates and target end dates)
- Custom fields configured in Jira (for example, single-line text fields)
Sample plan with the improved interface
Adding a column
To display issue details in a plan, you'll first need to add the relevant fields to the plan. These fields will be displayed as columns, and each column will contain the corresponding issue detail.
- In the fields section of the plan, click more ( ).
- Select the checkbox of the field you want to add. The field will be added to the plan as a column.
To remove a column, click more () > clear the checkbox of the column.
Setting a value or option
While planning work, you can set a value or option in the corresponding columns of a plan.
- Click the cell of the relevant column.
- Specify the value or option for it.
The values for the columns in your plan may depend on what's configured in your Jira instance. For example, your priority options will depend on the configuration of priority schemes in Jira.
There may be times when the options for a custom field (for example, checkbox fields or multiple-choice select fields) will not load in your plan. This happens if you're trying to choose an option for an issue that you have not saved in Jira just yet. You'll need to save the issue to Jira first, to make the options load in your plan.
Resize the columns in a plan to ensure that all issue details are displaying completely.
Sample collapsed column in a plan
- Hover over either end of a column.
- Drag the end of the column to resize it.
- If you resize a column and make it small enough, the column automatically collapses. Click the column name to expand it.
- To quickly collapse and expand a column, click its corresponding column header.
- To collapse all columns, click Fields in the fields section.
You can move the columns in the order that you want them to appear in a plan.
Reordering columns in a plan
- In the fields section of the plan, click more ( ).
- Hover over the column that you want to move until the drag icon appears.
- Drag and drop the column to where you want to position it.
By default, the issues in a plan are sorted by rank order. You can choose to sort issues by target dates, due dates, status, or by any other custom dates that have been configured to schedule the issues in the plan. After choosing how to sort issues, you can further sort them in either ascending or descending order.
Sample issues sorted by rank
Sample issues sorted by ascending target start dates
There are some rules to keep in mind when you're sorting issues in a plan.
The following rules apply regardless of how sorting is configured in a plan:
- Issues in the highest hierarchy level will be sorted first. The issues within each group down the hierarchy levels will then be sorted.
- If you've applied filters to a plan, the configured sorting order will still apply to any issues filtered out. If you clear the filters of the plan, all issues will be sorted in the configured order.
Once you've configured sorting for the issues in a plan, any newly created issue will also be sorted in that order.
For example, if issues are sorted by ascending target start dates, and you create a child story in an epic, the new child story will also be sorted using its target start date against the dates of the other issues in the epic.
Sorting issues by dates
The following rules apply when you sort issues by dates (target dates, due dates, or any custom dates):
If an issue doesn't have dates but is assigned to a sprint, the sprint dates will be used as the start and end dates of the issue. These dates will be used when the issues are sorted.
Since the issues are already sorted by dates in the relevant order, you won't be able to drag and drop an issue in the scope section of your plan. However, you can still adjust the dates of issues if needed, which may have an impact on how these issues are consequently sorted.
If you're sorting by dates in ascending order, any issues that don't have dates will be sorted first, and they will appear at the top of each sorted group.
If an issue has only one date set, then that issue will be sorted before any other issue that doesn't have any dates. The issue with one date will appear at the top of the sorted group.
Sorting issues by status
The following rules apply when you sort issues by status:
Issues in the highest hierarchy level will be sorted by status first. The issues within each group down the hierarchy levels will then be sorted.
- Within each hierarchy level, issues will be sorted first by status category (To do, In progress, and Done). Within each status category, issues will be sorted by status alphabetically, depending on whether you're sorting in ascending or descending order.
- Newly created issues that aren't saved in Jira yet are sorted in ascending order before issues that are already saved in Jira.
- Since the issues are already sorted by status in the relevant order, you won't be able to drag and drop an issue in the scope section of your plan.
Configuring sorting order on the roadmap
You can configure the sorting order of issues directly on the roadmap of a plan.
- Hover over the header of either the start date column or the end date column until the sorting icon appears.
- Click on the sorting icon until the issues are sorted in the order you want:
- Up icon for ascending order
- Down icon for descending order
- No icon to revert to the default rank order. Alternatively, if the issues are already sorted by ascending or descending order, click Reset sorting order to revert to the default rank order.
Configuring sorting order via view settings
You can also configure the sorting order of issues when customizing the view settings of a plan.
- In your plan, click the View settings drop-down.
- In the Sort by section, choose how you want the issues to be sorted by.
- Choose whether you want to sort the issue in either ascending or descending order. Note that you don't need to perform this step if you choose to sort issues by rank.