How to link different JPD projects / How to manage Contributor access

[Mart Postma]

The issue

While setting up my JPD project, I stumbled upon the following issue. 

As it unfortunately is not possible to currently just share one view or section with a (specific) stakeholder to gather ideas, insights or comments - is there a work-around suitable to mitigate this lack in functionality?

Another solution I was thinking of is creating two different JPD projects, one being internally used and the other one being externally used. Is it possible to use/link the idea issues to a different project in JPD? 

Does anyone have any other solutions or recommendations to achieve this functionality?

Current setup

 To clarify, I wish to share the "External" section with users from the user group "Contributors", and the "Internal" section should only be available to my team. Thus, I only want "Contributors" to have access to the "External" view, and not to the entire JPD project.

More types of users?

Is there any update/ETA available for this (The different types of users: Creators, Contributo... - Atlassian Community) addition of user roles? I think that this would be the functionality I am wishing to achieve.

[Tanguy Crusson · Accepted solution]

Hi @Mart Postma , here you go: https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Very-early-access-to-the-Stakeholder-Sharing-experience/ba-p/2459076

[Mart Postma]

Perfect, thank you. I have signed up for the early access. 

EDIT: @Tanguy Crusson - could you give me an update on the timeline for early access? What can we expect in terms of participation in the early access? It's essential for us to consider JPD as our product discovery tool in the future to be involved in it's development and testing.

[Hariharan Y]

There needs to be a way to hide views even from some internal teams. Planning on ideas discreetly by Product Management seems to be impossible. Is there a workaround on that?