How to configure the scheduling options
In this section, you can configure the work package sizes and concurrent work.
- Go to your plan > click located next to the plan name and go to Configure.
- Change the desired configuration.
|Issue assignee import level||
Defines up to which hierarchy level Portfolio tries to match the assignee of an issue to the corresponding person in the team member column.
This option allows you to set the level at which issue assignees in your Jira application are the people that will actually work on the issues.
Example: You might have the Product Manager assigned to an Epic and the individual developers assigned to Stories within the Epic. The Product Manager is not the person who is going to work on the implementation so we can set the assignee import level to Story. Portfolio will take the story assignees into account but not the epic assignees.
|Maximum assignees per story||
Defines the maximum number of people who can work on an individual story.
|Dependency scheduling||Defines how dependencies are ranked during scheduling. Learn more here.|
|Dependent story constraint||If set to 'On', work items with dependencies cannot be worked on concurrently. For Scrum teams, they will be scheduled in separate sprints. For Kanban teams, they'll be scheduled on separate days. If this option is disabled, work items with dependencies can be worked on at the same time. In both cases, the dependent work items can never start before their predecessors|
|Enforce concurrent work||
When you set this option to On, and if multiple team members are assigned to a single item, the scheduling algorithm ensures that all the work for that item is scheduled into a single sprint.
|Stage sprint constraint||If set to 'On', the separate stages of a work item are scheduled sequentially into separate sprints. If set to 'Off', work on multiple stages can happen in parallel in the same sprint.|
|Minimum work package size||
Defines the minimum work package size for all the items above the story level. This setting prevents free capacities from being up with unrealistically small work packages, which would not exist once a high-level work item is broken down into stories.
Example: Set it to 0 to maximize capacity filling.