I found a defect in new version of Portfolio that impacts its use if the teams are using sub-tasks in JIRA
The defect is exposed in two ways:
1) If the sub-tasks have dependencies upon one another, Portfolio will not schedule the story.
2) If the sub-tasks do not have dependencies upon one another, Portfolio will schedule the resources concurrently.
Example:
- There is a story with three sub-tasks: Design (2 days), Develop (3 days) and Test (4 days).
- If the sub-tasks are set up so that design blocks development and development blocks testing, Portfolio will not schedule the story and produce errors that there is a violation in dependencies and cyclic dependency detected.
- If the dependencies are removed, Portfolio will schedule all the resources concurrently. In this example, that would make it appear the designer is working on the story for 9 days and that all resources will start working on the story on the same day.
- The setting 'Issue assignee import level' in configuration does not address this.
I communicated this to Atlassian and they have logged it as a suggestion.
