Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How do Portfolio teams work?

Markus
Contributor
February 4, 2019
If we create a plan and import a project the roadmap gets very messy because portfolio doesn’t take our planned sprints into consideration.

If we import a Board and assign people to a board we get the same problem: User stories switch sprints without any visible reason and it’s also quiet messy.

BUT if we import a board and don’t assign any people to the team it’s working perfectly, our sprints are taken into consideration and it works exactly like it should be.

Now the big question is: what’s the reason for this behavior?

Let’s ignore importing project cause it’s not recommended but what’s up with the behavior when assigning people to a team?

I suspect (and it’s a wild guess) that portfolio takes the other user stories (outside of the plan) that are assigned to a user also into consideration.

Can this be? That portfolio recognizes that a member of a team inside a plan has also to work on other user stories that aren’t part of the plan?

It would explain it but I’m not too sure about it.

Anyone who knows more?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
atlassian, team '25 europe, atlassian event, barcelona 2025, jira, confluence, atlassian intelligence, rovo, ai-powered collaboration, developer tools, agile teams, digital transformation, teamwork solutions, atlassian conference, product announcements

🌆 Team '25 Europe registration is now open!

Join the largest European gathering of the Atlassian Community and reimagine what’s possible when great teams and transformative technology come together. Plus, grab your Super Fan ticket now and save over €1,000 on your pass before prices rise on 3 June.

Register now
AUG Leaders

Atlassian Community Events