How do I assign idea back to the contributor in JIRA Product discovery?

Question

We are trying out the JIRA Product discovery module. And I am wondering how to assign an issue back to a contributor? This situation arises when more information is required from the contributor and would need to routed back to them to provide the information and move the idea to the next step. Is this possible? If not, what is the workaround? Thank you.

Hariharan Y_wxz5fk · Answer

They don't have JIRA Licenses as they are not part of Product/Engg. I have added them to the contributors group for the Product discovery module in JIRA. I do not require them to Edit an idea after submission, but would just want to assign it back to them so they can provide their comments as responses to our questions.

Tanguy Crusson · Answer

Hi @Hariharan Y : contributors can create ideas, but you should think of it more like a "submission form" - they can submit it, not edit it after the fact.

It's a bit wonky, we're discussing where we take it next.

In the meantime, I can see 2 options:

* If these contributors have a Jira license (any Jira, doesn't have to be Jira Product Discovery) - then you can ask them questions via comments (you mention them in the comments with your question, they receive a notification, they can reply back and you'll be notified)
* If they don't, then you can't assign ideas to them and they won't receive notifications when mentioned in comments. But you can create an automation rule that sends them a notification/email when you need more info (for example after moving the idea to a "needs more info" status, or based on a field value)

An alternative we recommend for scenarios like this is to separate your product discovery project from the process where people can make requests. That's what we use in our team.

* We have a Jira Service Management form/queue where people can ask things or send feedback
* We have a Jira Product Discovery project with all our product ideas and roadmaps
* When someone requests something, it lands as a ticket in the JSM queue, we look at it, we ask questions to the requestor by replying to the JSM ticket, then if we want to action it we add it as an insight to the idea (using the Chrome extension)

This provides a clean separation between what people ask for, and the place where we have all product discussions. Otherwise if we let people create ideas in our product discovery project directly, it would become a mess really quickly.