You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We are rolling out two new projects - a JSM project to allow our customers to submit tickets and a Discovery project where customers can vote on features. How can I set up permissions to let the Customer users from JSM see the Discovery project too?
When you say "Discovery", you are referring to a Jira Product Discovery project here, is that right?
Well, theoretically you would have to set access to your JPD project accordingly - that is, give your customer group. But, before you proceed, please check out this info if you haven't seen it already:
https://community.atlassian.com/t5/Jira-Product-Discovery-articles/A-big-update-on-Jira-Product-Discovery-pricing-creators-and/ba-p/2304729
Bottom line: JPD is near GA and currently undergoing some heavy changes to access/roles and all that. The linked topic shows a preview of how things will look to external stakeholders, but right now, it's not exactly working like that, just yet.
Consider to post your question in the JPD group, though! Maybe the team or other users can share some more concrete advice.
Hope this helps, yet least somewhat ...
Yes, "Discovery" = "Jira Product Discovery"
Can you elaborate on "Well, theoretically you would have to set access to your JPD project accordingly - that is, give your customer group"?
- How do I set access accordingly?
Thank you for the article. I will take a look. We need to roll out Jira Product Discovery before 5/21 when our current vendor subscription ends.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Sheri LarsenJPD uses team-managed projects. So in the project settings, you can set which users and which groups can access the project, and in which role (contributor or viewer).
The other feature that may relate to your scenario is sharing views. That's via the "Share" button in each view.
However, all this isn't ready yet for you to actually share JPD with external stakeholders. Viewer access come close, but it may not be quite what you want. You should try.
Like Tanguy stated in the linked topic, features for external stakeholder access seem to come only after JPD ends beta and goes GA. I can't say when that will be. But since the JPD team is in "all hands on deck" mode, and also, an announcement at Team 23 was made, I believe it's rather a matter of days or a few weeks at most.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, of course I tried what you suggest but Customer users from JSU don't appear there in anyway. That's why I came to the community, Can you elaborate on how to see Customer users from the Discovery Access settings?
Is there any rough idea when the GA release for JPD will be?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.