Mapping issue assignees to team members

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

This page discusses the usage of Portfolio for Jira live plans (any version from 2.0 to 2.27). If you're using the redesigned planning interface, see this page instead.

You can define the hierarchy level up to which Portfolio for Jira will try to match the assignee of an issue to the corresponding member of the team. Specify the level at which the issue assignees in your Jira application are indeed the people who will actually work on the issues.

For example, you may have the Product Manager assigned to an epic, and individual developers assigned to the stories within that epic. In reality, the Product Manager won't really be the person working on the stories, since it will be the developers themselves. You can then set the issue assignee import level to story , in this case. Portfolio for Jira will then take the story assignees into account, but not the epic assignees.


For the Jira issue assignee to show in the team member column in Portfolio for Jira, these conditions must apply:

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

    Before calculating your plan, note that for the assignee to display, the issue must have either an estimate, or a sprint manually associated to 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.


To define the issue assignee import level:

  1. Go to your plan via Portfolio (in header) > View Portfolio > click your plan.
  2. Click  more ( ) next to the plan name >  Configure >  Scheduling.
  3. In the scheduling options section, go to the issue assignee import level menu, and select the level.


To set an assignee as a team member:

You can manually set an issue assignee in Portfolio for Jira, and update the Jira issue once you commit the change.

  1. Go to your plan via Portfolio (in header) > View Portfolio > click your plan.
  2. Click  more ( ) next to the plan name >  Configure >  Commit of changes.
  3. To commit issue assignees from Portfolio for Jira into Jira, click On.

(info) Note that if you select off, whenever you change an issue assignee in Portfolio for Jira, this won't affect the Jira assignee, even if you commit changes.

関連トピック

最終更新日 2019 年 9 月 20 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.