Assignee got resetted all the time :/

[Sebastian Pechhold]

First of all, i want to thank @Tanguy Crusson and the Atlassian community for their willing to help.

My issue

After assigning an idea to an assignee, it is resetted the whole time with the following message:

The message is confusing, because the idea is already created. Just want to update the assignee field. But everytime i reload the page, the assignment got lost. What do i do wrong?

Help is always appreciated :D

[Tanguy Crusson · Accepted solution]

Hi all, it looks like this issue's been open for a while and it slipped through the cracks, we apologize!

Basically this happens because you are trying to assign an idea to someone who is not a creator (doesn't have a license for Jira Product Discovery). You can only assign ideas to licensed users (it's deep in the Jira platform, not something we have control over). 

We are looking into it now - but the way we'll fix that is to make sure these users don't appear in the dropdown. A workaround we recommend for this, if you want to assign ideas to contributors, is that you create a separate field of type "People". Contributors are available for selection there. 

[Tanguy Crusson]

OK that should be fixed now

[Rohan Swami]

@Jaime Laird you can send a recording directly to my email rswami@atlassian.com

[Jaime Laird]

Thank you!

[Idan Ben-Arieh]

I'm having the exact same issue. It's a show stopper for us. Any advice on this? 

[Jaime Laird]

@Idan Ben-Arieh I am still waiting for a resolution... @Sebastian Pechhold did you ever get this resolved in your account? @Rohan Swami we really need a solution to this bug.

[Idan Ben-Arieh]

@Jaime Laird  - Just heard back. They said "The issue you're seeing is happening likely because the assignee field will only accept Creators. This is due to the assignee field being a Jira-wide system field and those can only receive licensed users (i.e. creators)."

[Jaime Laird]

Thanks @Idan Ben-Arieh ! This is definitely a disappointing UX limitation. Did the response indicate any appetite to address this, or is this just being accepted as an inherent Jira limitation?

[Sebastian Pechhold]

@Jaime Laird  Yes but with a workaround. Create a new field (@PEOPLE) and call it what ever you need. We choose "Developer". Just mention them there in this field.

The problem is, that "real" assignees need to be added to JPD with product access.

[Rohan Swami]

@Jaime Laird we don't have an active bug in this area. If you can share a screen recording (eg. Loom) of what you're seeing in the app then we might be able to diagnose. Alternatively you can create a support ticket.

[Jaime Laird]

@Rohan Swami the issue is the exact same as what was reported by Sebastian here. I am not comfortable posting a screen recording to this public forum as the views contain our real data. When I go to support.atlassian.com and begin to create a request, I am only offered the community or how to guides (see attached). Can you please provide instructions for me to open a private support request? Ideally I would like live support where I can screen share.

[Rohan Swami]

Hi @Sebastian Pechhold do you have filters in this view? We can take a look at your view if you raise a support ticket at support.atlassian.com 

[Sebastian Pechhold]

Hi @Rohan Swami ,

no we do not have filters active.

Do i have to add assignees as contributors to JPD?

[Sebastian Pechhold]

Added the assignee as contributor. Did not work.

[Rohan Swami]

Hi @Sebastian Pechhold please raise a support ticket with us at support.atlassian.com and we'll investigate

[Sebastian Pechhold]

I did :) Thanks

[Jaime Laird]

@Rohan Swami I am having the exact same issue - did the support request from @Sebastian Pechhold get resolved?