Changing assignee in JIRA doesn't reflect new assignee in Portfolio

[Maneesha Syea]

I am using Portfolio with JIRA. When I change the team member assigned to a task in Portfolio and commit the change, it is immediately reflected on the JIRA task.

But if I change the assignee on the JIRA task and refresh my Portfolio plan, i don't see the change.

Can someone please guide how to synchronise the change? Or this is a bug in Portfolio?

Thanks.

Maneesha

[Shannon S · Accepted solution]

Hello everyone!

This turned out to be a bug, which I will link below:

• JPOCLOUD-2071 Issues being scheduled for a wrong person in Portfolio Plan

Please vote on the bug if the same has affected you, and watch it for any updates in the future.

Regards,

Shannon

[Maneesha Syea]

Hi Shannon,

It would be great if support can resolve this issue.  My Portfolio version is 1001.0.0-SNAPSHOT.

Thanks.

Maneesha

[Shannon S]

Maneesha,

Thank you for confirming you're on the Cloud version.

I have created a case with our Cloud support team and they will have a look for you.

Once resolved you can feel free to post the solution here as it will help other users in the future.

Regards,

Shannon

[Maneesha Syea]

Thanks Shanon.

How will I know when it has been resolved?

Maneesha

[Shannon S]

Hi Maneesha,

I created a support ticket for you in our system with your email address. You should have received the creation email by now. 

You will know when it's resolved because you're included on the support ticket and will be receiving emails from us. Keep an eye on your email for any responses from the team, as they will likely need more information from you to proceed. 

Regards,

Shannon

[Maneesha Syea]

Hi Shanon,

I didn't get any mail for the support ticket and no one has contacted me yet for questions.

Can you please check again if my id is correct on the ticket?

Thanks

Maneesha

[Shannon S]

Hi Maneesha,

It's using the same email address you're using here, so if you haven't received emails from that you may want to check your spam filter or with your email server admin.

However, I can tell you it has since been confirmed that it is an existing bug.

From our correspondence with you:

It looks like you're running into an existing bug, which can be found here:

JPOCLOUD-2071: Issues being scheduled for a wrong person in Portfolio Plan

Please be sure to watch it, so that you are notified when this is fixed in a future release. If you would like to know how we prioritize the fix of bugs, you can find all the details on the Bug Fixing policy policy page.

You can also add a public comment to the bug itself, if there are any additional information you would like to share with the developers directly so that the team can take that into account while addressing the problem. The development team is particularly interested to understand the use case for this request (e.g. how is this affecting you? who in the organization is affected by the problem?). I already linked your ticket to the bug report, and the developers are already across your comments.

Please let me know if you have any questions or remarks.

If you login to to our support portal you should be able to access your ticket and add any follow-up remarks if needed.

Regards,

Shannon

[Maneesha Syea]

Thanks Shanon.  I'll be watching the JIRA ticket.

Regards,

Maneesha

[Shannon S]

You're welcome, Maneesha!

Happy to help.

Regards,

Shannon

[Vaishali Patil]

Hello!,

Was this issue resolved?

We have recently started using Portfolio and Jira and are running across the same issue. It looks like it is a one way sync from Portfolio to Jira. Once you set the member in Portfolio and sync it to Jira it will no longer sync in the other direction.

Thanks,

Vaishali

[Shannon S]

Vaishali,

Thank you for reaching out. I checked the support ticket, and it was reported as a bug. I have added a link to that bug in a separate answer on this thread, but you can also find it below:

JPOCLOUD-2071 Issues being scheduled for a wrong person in Portfolio Plan

Please vote on this and watch it to be informed of any updates.

Best regards,

Shannon

[Michael David]

Hi @Shannon S When can we expect this issue to be resolved? I think it's important that Portfolio reflects the correct assignee if updated in JIRA, especially if the assignee is part of the Portfolio team.

When the assignee is changed in JIRA and I re-calculate in portfolio, the team member for the tickets should update accordingly. 

[Shannon S]

Hi Maneesha,

Have you re-calculated since changing assignee?  That needs to happen first in order to show.

Besides that, have a look at this article:

• Map an issue assignee to a team member

In addition, the issue assignee import level must be set to a hierarchy level. See Configuring initiatives and other hierarchy levels.

Let us know if you have any questions!

Regards,

Shannon

[Maneesha Syea]

Hi Shannon,

Thanks for the guide. I have actually done all of these but the assignee still doesn't change.

My issue assignee import level is set to Story.  I changed the assignee of a story in JIRA Software. Refreshing and recalculating in Portfolio does not reflect the change.

I am not sure what else can be done here.

Maneesha

[Shannon S]

Hi Maneesha,

Is the issue assigned a team, and is the expected assignee is part of a team that can work on that issue? Has the issue “team member” been set to calculate (does not have a set value)?

Regards,
Shannon

[Maneesha Syea]

Hi Shannon,

Is the issue assigned a team? yes

is the expected assignee is part of a team that can work on that issue? yes

Has the issue “team member” been set to calculate (does not have a set value)? yes

Although for the last question, what if an assignee was set and then changed in JIRA?  In any case i think it should be updated in Portfolio but it's not happening.

Thanks.

Maneesha

[Shannon S]

Maneesha,

Thank you for confirming. I want to send this to our support team so we can dig further into your issue, but I'll need to know your Portfolio version. Could you let me know what that is?

Shannon