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
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
Will there be a customer "Portal" feature to allow for customer feature requests, feedback, voting, etc. I think I have read in the past the JSM would fill that gap (no sure where I read this), but that would put different a different user group (DevOps/Development vs Product) into yet another tool.
@Ken Young this is something we're currently exploring. We're starting with internal collaboration in mind first (a way to engage people from outside the product team but in the same company), and will explore external collaboration later.
Thank you @Tanguy Crusson . I thought I read early on that this was going to explored/roadmap. I know our product teams appreciate this capability in both Aha! and ProductBoard. My goal is to be able to tie this capability (in Jira Product Discovery) in a much tighter fashion to our development workflows in Jira/Advanced Roadmaps.
Hi @Tanguy Crusson is there any update on the Portal functionality for JPD? For me, and I'm sure many others, it makes total sense for Jira to build out this much added piece of the Discovery process. Otherwise, PM's are faced with using other products such as Product Board, Aha etc, just because they offer the portal feature. Most of us use Jira for Delivery, so we just want to use one tool for Discovery!
So far, you can integrate JPD with the Customer Case for Jira and create a public portal for collecting feedback from customers. Every idea on the portal goes automatically into a JPD project. You can also create a private portal with email domain or specific email restrictions.
Hi @Ken Young
If you need the functionality of a public forum where all the tickets are visible to everybody, you can check Customer Case for Jira app. It is a portal for your external clients where they can submit their issues or ideas and vote for them. It can be public (visible to everybody), private (restricted for specific email addresses or domains, for example, for your internal needs), or you can set it up as a support service just as JSM(private communication with a support assistant).
@Brant Schroeder - Can you provide a little more detail on what Atlassian does currently? Do you have to duplicate all the tickets in a separate project? Or do they live in this public facing project for voting, but then are created in a different project for actual development work?
This is the biggest gap we have with Jira. Not being able to expose our ideas and requested features to our customers for input.
It seems like, if a tool is being developed specifically for product discovery, a feature to allow input/feedback from our customers would be a natural fit.
@David I do not work for Atlassian but I believe that they have set up a public project. On server, you used to be able to set up a public project and allow anonymous voting. On cloud you can create public projects but I do not think you can vote on issues.
Public Projects in Cloud - https://support.atlassian.com/jira-cloud-administration/docs/allow-anonymous-access-to-projects/
Atlassian seems to be using a combination of the public sites and licensed users to submit and upvote issues on the cloud.
I am creating a jira project to use as an ideas portal that allows voting to fill this need. Additionally I plan it implement an issue collector and a form overlay for external users to submit ideas. I do not yet know of a way to do this in JPD, but I would love that functionality.