You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have Teams with only one Person, and per Definition is a parallel work not allow. From time to time Portolio plan and calculate this resouce to a parallel work. Is this a configration Problem or a known Problem ?
Portfolio is going to attempt to schedule as much work as a user can complete based on the scheduling factors input for the user and issues. Described in more detail at the following links, noting one is for server and one is for cloud, but the two docs describe the same behavior in alternate ways and I recomend checking out both versions as the functionality overlaps between the platforms in this particular article:
To remove the ability for the user to be able to run parallel tasks I would recomend setting up dependencies on the issues so that the next issue cannot be scheduled until the first issue is expected to be completed. details on setting up dependencies can be seen here:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.