How to configure errors and warnings
Portfolio for Jira allows you to configure the errors and warnings that are displayed in your plan. These errors and warnings have been found when Portfolio has calculated your schedule after you have clicked the 'Calculate' button. They can be triggered by a number of factors including resourcing availability, sprint capacity, dependencies between issues and more.
Errors imply that an issue can't be scheduled at all. For example, when an issue and its sub-tasks are assigned to different releases, it will not be scheduled.
Warnings imply that an issue is scheduled, but with some sort of limitation. For example, when an issue has people assigned who have limited availability, it is scheduled, but only a portion of it.
In the following section, you will learn how to turn these messages on and off as well as their meaning
- Go to your plan > click
located next to the plan name and go to Configure > Scheduling. - In this section, you can define whether you want errors, errors and warnings or none of them displayed in your plan.
Click more (
) next to the plan name > Configure > Scheduling.- Select one of the following options for warning levels:
- Errors only — Only errors will be displayed in your plan if any issue happens.
- Errors and warnings — Both error and warnings will be displayed for any issue that happens in your plan.
- None — No messages will be displayed for any issue that happens in your plan.
Errors and warnings description
| Scheduling messages | ||
|---|---|---|
| Message | Level | Description |
| This issue is partially scheduled because the assigned people have limited availability | WARNING | Check that someone in your team is available to work on this issue at this particular time and then recalculate your plan. |
| Your schedule can't be calculated properly because it exceeds the planning horizon | ERROR | Every plan has a maximum 5-year planning horizon. Decrease the scope of work, add extra people, or increase your team's capacity to reduce the length of your schedule. Then, recalculate your plan. |
| This issue can't be scheduled because this issue and its sub-tasks are assigned to different releases | ERROR | A story-level issue and its sub-tasks must be assigned to the same release. Check the release assignments are consistent and then recalculate your plan. |
| This issue's assignee is ignored because they aren't part of the plan | WARNING | This issue is scheduled for another person than its assignee, as the assignee is not part of any of the teams in your plan. Check that they are part of a team and that their team can be assigned to this issue. Then, recalculate your plan. |
| This issue can't be scheduled properly because the assigned team isn't present in your plan | ERROR | Change the assigned team to one that's in your plan or add the assigned team to your plan. Then, recalculate your plan. |
This issue can't be scheduled due to a problem with one of this issue's sub-tasks. | ERROR | Resolve any errors on issues: [ISSUE-KEY], [ISSUE-KEY] and [ISSUE-KEY]. Then, recalculate your plan. |
| This issue can't be scheduled because this issue and its sub-tasks are assigned to different teams | ERROR | A story-level issue and its sub-tasks must be scheduled to the same team. Check the team assignments are consistent and then recalculate your plan. |
| Sprint messages | ||
| Messages | Level | Descriptions |
| More than one sprint is needed to finish this issue | WARNING | Break your story down further so that estimate is reduced, or decrease the scope of the sprint until this issue fits into the sprint. Then, recalculate your plan. |
| This issue can't be scheduled because its sprint is invalid | ERROR | [SPRINT-NAME] is ignored because it is invalid. Either, assign this issue to another sprint, or change the sprint's dates in Jira. Then, recalculate your plan. |
| This issue can't be scheduled because its sprint is overlapped by another sprint | ERROR | [SPRINT-NAME] is ignored because it is completely overlapped by [OTHER-SPRINT-NAME]. Either, assign this issue to another sprint, change the sprints' dates in Jira, or [exclude [OTHER-SPRINT-NAME] from team [TEAM-NAME]](LINK-TO-MODAL). Then, recalculate your plan. |
| This issue's earliest start date is ignored because of its sprint assignment | WARNING | The start date of this issue's manually assigned sprint takes precedence over this issue's earliest start date. To maintain the earliest start date, set the issue's sprint to 'Calculate'. Or, to remove this message, remove the start date from this issue. Then, recalculate your plan. |
| The people working on this issue are overbooked for this sprint | WARNING | This issue is manually assigned to a sprint in which the people available to work on it are overbooked. Decrease the scope of those particular people. Or, if there are no people on your team, decrease the scope of the sprint. Then, recalculate your plan. |
| Resource messages | ||
| Messages | Level | Description |
| This issue can't be scheduled because no one is available | ERROR | Check that someone in your team is available to work on this issue at this time and then recalculate your plan. |
| This issue can't be scheduled because people with the necessary skills aren't available | ERROR | Story-level issues can't be assigned across teams. The team needs to have all required skills and availability within its members. Assign these skills to people and make sure they're available to work on this issue. Or, remove the skill requirements on this issue by refining the estimates. |
| Dependencies messages | ||
| Messages | Level | Description |
| This issue can't be scheduled because it depends on an issue that could not be scheduled | ERROR | There are problems scheduling issues this issue depends on [ISSUE-KEY], [ISSUE-KEY] and [ISSUE-KEY]. Resolve the problems on these issues and then recalculate your plan. |
| This issue's dependencies are ignored due to its release assignment | WARNING | This issue's manually assigned release is scheduled earlier than this issue's dependencies. This makes it impossible to honor those dependencies:[ISSUE-KEY], [ISSUE-KEY] and [ISSUE-KEY]. Either set this issue's release to 'Calculate', or remove the ignored dependencies. Then, recalculate your plan. |
| This issue's dependencies are ignored due its sprint assignment | WARNING | This issue's manually assigned sprint is scheduled earlier than this issue's dependencies. This makes it impossible to honor those dependencies: [ISSUE-KEY], [ISSUE-KEY] and [ISSUE-KEY]. Either set this issue's release to 'Calculate', or remove the ignored dependencies. Then, recalculate your plan. |
| This issue can't be scheduled due to a cyclic dependency | ERROR | This issue depends on an issue that directly (or indirectly) depends back on this issue. Remove that dependency and then recalculate your plan. |
| This issue can't be scheduled due to dependencies between its sub-tasks | ERROR | Portfolio can't process dependencies between sub-tasks within a single issue. Remove these dependencies on this issue and then recalculate your plan. |
| Skills messages | ||
| Messages | Level | Description |
| This sub-task can't be scheduled because no available single team member has the required skill set | ERROR | Sub-tasks must to assigned to a single person and can't be assigned to teams or people. Check a single team member has the required skill set and make sure they are available. Or, remove the skill requirements on this issue by refining its estimates. Then, recalculate your plan. |
| This issue can't be scheduled because the available team members don't have the required skill set | ERROR | Story-level issues can't be assigned across teams. Check that (a subset of) team members collectively have the required skillset, and that they are available. Then, recalculate your plan. |
| This issue can't be scheduled because the available people don't have the required skillset | ERROR | Check that (a subset of) people collectively have the required skillset and that they are available. Then, recalculate your plan. |
| Other/general messages | ||
| Messages | Level | Description |
| This issue can't be scheduled because this issue's estimate is too small | ERROR | Check all estimates on this issue are at least 0.01. This means the total estimate, as well as the estimate for any stage or skill. Then, recalculate your plan. |
| This issue can't be scheduled because the calculation is too complex | ERROR | Remove the issue from its assigned sprint, change the required skills, or make the assigned team smaller. Then, recalculate your plan. |