Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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.

Atlassian Community about banner
4,466,380
Community Members
 
Community Events
176
Community Groups

Cant map an issue assignee to a team member in Portfolio

I choose assignee for story or task or bug or sub-tusk in Jira Cloud from team members in my Portfolio plan, then click calculate in Portfolio and nothing changes (team, fix version, components - are updated but assignee - is not)

 

I found some information in:

https://confluence.atlassian.com/jiraportfoliocloud/map-an-issue-assignee-to-a-team-member-868977839.html?_ga=2.166300923.418106851.1522046235-1328946415.1512994475

 

In order for the Jira issue assignee to show in Portfolio's team member column, these conditions must apply:

  • There is not member set in Portfolio.    Done
  • The assignee is set on the issue in Jira Software. Done
  •  The assignee is part of a team in your Portfolio plan. Done
  • If you've made a manual team assignment, make sure the assignee is part of that team. Done
  • To see the assignee that is being pulled from Jira Software, you have to Calculate your plan. Done
  • The issue assignee import level must be set to a hierarchy level. See Configuring initiatives and other hierarchy levels. Set in Story level

 

What am I doing wrong?

1 answer

0 votes
shafqat Atlassian Team Apr 26, 2018

Hi Sergey,

It sounds like it should work as you described. There could be a bug or a configuration issue causing this problem. Could you create a support ticket so that we may investigate this further: https://support.atlassian.com/contact/

Thanks,

The Portfolio for Jira Team

Running into the same issue not all assignee's are being pulled into portfolio at the story level.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events