Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Portfolio not sorting out teams properly? Need help!

Hi,


Just setting up a new portfolio plan. I'm creating new teams based off of different scrum boards. Setting everything up seems fine. I create new teams, assign boards to teams, and generate the initial plan.

My issue is that, after setting everything up and sorting the roadmap view by team, the teams aren't listed on the side — it just groups everything into an "unassigned" group (see screenshot).

I have multiple scrum teams that are label based on pull issues from the same project, but I thought the team sorting was done based off of board filter?

Am I missing something here? Any help would be greatly appreciated as this is confusing me quite a bit.

Screen Shot 2019-08-22 at 11.01.45 AM.png

1 answer

0 votes

Hi Tyler,

Thanks for reaching out and looking at your question:

I thought the team sorting was done based off of board filter?

This is touched on In the changes in the New interface Overview documentation:

In Portfolio for Jira, plans use the concept of team members, which are independent from assignees in Jira. You'd first assign an issue to a team member in Portfolio for Jira, and when you save this change to Jira, the issue is then assigned to the corresponding assignee in Jira.

In the improved interface, we're simplifying this task by letting you set the assignee directly in your plan. This effectively removes that extra step of assigning the issue to a team member first, then saving the change in Jira as an assignee change. One thing to note though — you can now assign an issue to only one assignee in the improved interface.

To elaborate on this a bit now the the Teams are set on the issue via the "Team" field manually based on the assignee and the teams do not automatically pull from the board associated to the team as they did in live plans,

Details on assigning work to a team is covered in This Document but you can add the team field as a column using the the 3 dot menu drop down at the top of the right most column here:

Screen Shot 2019-08-23 at 1.48.17 PM.png

After adding the column something that may be occuring is if the teams are missing a value in the field, From the behavior you described this should be the case but can can you check and confirm if this is indeed the case.  Next you can either set the team manually as covered in the article or you can leverage the Auto scheduler to populate the values in mass once you have estimates in place:

Screen Shot 2019-08-23 at 3.31.11 PM.png     &     Screen Shot 2019-08-23 at 3.35.45 PM.png

Regards,
Earl

I thought about this, too, but I'm still adding team members to each team, assigning them, and it's not working.

Ah, I think I figured it out, thanks!

Like Earl McCutcheon likes this

how do i get the team sorting. i have created the portfolio based on the project dashboard which has been created for each team. All issues are grouped under the unassigned even when i group by team. the team is having blank values, when i included this field

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you