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,463,198
Community Members
 
Community Events
176
Community Groups

Task issues assignee not imported in portfolio if skills enabled

Edited

In portfolio, I have created a team and each team member has a skill. If I create a task, in jira software, and i set the assignee, in portfolio the member is not imported even if i have correctly set the hierarchy import level.

Is there a way to fix this problem? thanks in advance

 

1 answer

0 votes

Hi Antonio,

There are few different things to check for what may be occuring here.  Refer to the "Map an issue assignee to a team member" documentation the items to check, noting:

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.
  • The assignee is set on the issue in Jira Software.
  •  The assignee is part of a team in your Portfolio plan.
  • If you've made a manual team assignment, make sure the assignee is part of that team.
  • To see the assignee that is being pulled from Jira Software, you have toCalculateyour plan.
  • The issue assignee import level must be set to a hierarchy level. See Configuring initiatives and other hierarchy levels.

Regards,
Earl

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events