Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,559,089
Community Members
 
Community Events
184
Community Groups

Portfolio parallel tasks

Edited
Ralf Chaloupka Admin
Ralf Chaloupka Admin Aug 05, 2019

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 ?

 

BR

Ralf

 

Answer
Watch
Like Be the first to like this
330 views

1 answer

1 vote
Earl McCutcheon
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 09, 2019

Hi Ralf,

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:

Regards,
Earl

Reply

Suggest an answer

Log in or Sign up to answer
Portfolio for Jira
Advanced Roadmaps
TAGS
AUG Leaders

Atlassian Community Events

See all events