Multiple separate stakeholders

[Fredrik Ernander]

I am evaluating Jira Product Discovery for a scenario where we have ideas coming in from multiple stakeholders who we need to have separate for business reasons but still plan the work for with a total overview. 

The use cases I'm not sure how to solve yet are the following :

• Choosing ideas from one stakeholder to line up for other stakeholders and discuss and keep track of that the discussion has happened
• Creating a roadmap from planned ideas per stakeholder (a filtered version of the total roadmap)
• Making sure that no stakeholder can see the names of the other stakeholders in their roadmasp/lists
  • But we need fields for that to keep track of who the idea is for 

Any ideas/recommendations/articles/clips which you could recommend me to go through?

[Denis Paul]

Based on the given info I would implement it like this:

• Use workflow states to reflect the stages of discussion (New, Ready for discussion, Discussed, Rejected, Approved, ...)
• Use labels for the different stakeholders. You can have codenames (Team A, B, C, ...) so noone will know who you work for. This way you can build filtered roadmaps but still have an overall view
• The name of the ticket creator will be visible in the ticket unless you use automation to create ideas. You need to use restricted views so different persons don't see each other's views. But this is a premium feature as dscribed in https://support.atlassian.com/jira-product-discovery/docs/view-permissions/.