Assignee field for CONTRIBUTORS

[Mark Moline]

We would like to assign idea tickets to CONTRIBUTORS.

The product manager is a creator. All devs are contributors.

In our ideal workflow, the product manager assigns JPD tickets to a CONTRIBUTOR for them to add comments/insights.

We need to use the assignee field since that's how our users find the tickets they're supposed to be working on across all our Jira projects via the "Your Work" page and other custom filters.

In the case of JPD, they're not creating new ideas or fields or views, etc. They're just commenting/insights on the issue.

Am I missing something or is this the intended behavior? Can we change it?

[YY Brother]

Hi @Mark Moline 

Welcome to our Community.

I think it's the intended behavior.

In JPD, creators are licensed while contributors are unlicensed and defined as collaborators of the creators. In Jira practice, if product managers as creators want to involve developers in their ideas, then PMs mention develops through Jira comments.

In my practice, I write a comment too, but I will add the develper as the watcher of this ideas. If we has a dashboard gadget to list all my watched issues, then the developers can use it to see all their watched ideas/issue/tickets through Jira dashboard.

Hope it helps you & Thanks,

YY哥

[Mark Moline]

Thanks for the input, everyone. The ideal solution still remains populating the Assignee field in JPD with non-creators. That's the simplest solution to ensuring everyone can always see all the tasks where their input is required.

Barring that, we've created a new SubjectMatterExpert field and are populating that with the developer responsible for commenting on the issue. Then creating a new task ticket for that dev that links to the JPD ticket. It's kludgy but I guess it's what we have for now.

Still holding out hope Atlassian fixes this one for us.

[Karin van Driel]

Why not create a task in Jira for the user that links to the JPD idea? We have the Owning Product Manager be the Assignee of ideas they own, which I feel is the intended use of the Assignee field, but I could be wrong there.
Also, doesn't it make sense to put a task in the user's backlog, if they are a dev, so that it counts towards capacity? You could even create an automation that would create the task based on setting a value for the Contributor, if you add that as a field. Just a thought :) 

[Tere Pile]

Its a good use case - while likely expanding the requirement some, I could see this also allowing an assignee (contributor) the ability to edit 'key' fields (as an example) not critical.  I've been playing w/a means to have some contributors do xyz and others just do x (all can create)