Jira portfolio (Cloud) doesn't map Jira issue assignee

[Massimo Carucci]

Despite what is reported in the documentation is valid, Portfolio does not recover the assignee from Jira Issue

I made the following checks and the rules are respected, namely:
- There is not member set in Portfolio (set to calculated)
- 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.
- Calculate your plan.
- The issue assignee import level must be set to a hierarchy level. (set to Story)

I also tried to set up a sprint where the resource on the tk jira is available in terms of capacity

Does anyone have any suggestions? Is there a bug?

Thanks in advance

[Earl McCutcheon]

HI Massimo,

Thanks for bringing this up, the disconnect seems to be coming from an inconsistency in the docs for this feature, and the cloud documentation is missing this information, but its covered in the Server version of the doc and applies to both platforms, I'm working with the documentation team to get the info updated accordingly on both doc version:

• Cloud Documentation: Mapping issue assignees to team members
• Server Documentation: Mapping issue assignees to team members

It's going to come down to having a weighted item that the calculation can run against before the calculations will run for the assignee association to occur, Either Sprint or Estimate being set.  For this operation the calculate option is looking to see if the issue can be scheduled as the first step looking at the estimates, and if it cannot be added to the schedule as there are no items to pick up the rest of the calculation is skipped.  The Section noting the specifics is:

Before calculating your plan, note that for the assignee to display, the issue must have either anestimate, or asprint manually associatedto it.

Depending on how unestimated items are scheduled in your plan, these details are required for calculation to work and display the assignee:

• Based on default estimates: Values must already be set as default estimates for all hierarchy levels.
• Based on target dates: The issue must be estimated, or must have a sprint manually associated to it.
• Custom: The issue must be estimated, or must have a sprint manually associated to it.
• Off: The issue must be estimated.

Regards,
Earl