Have a best practice you want to share or a question about Productboard? Ask here.
- 303 Topics
- 960 Replies
Hello Makers community, after reading messages in community, checking support documentation and academy recordings, I can not find my answer so it is time to ask help!I would like to provide some statuses of feedback and insights for each release globally: how many insights we delivered in this specific release? These are linked to features obviously and we can have KPI of features released but how to access easily and visually of insights delivered?I could have the same question and need by customers too: how many insights we delivered for this particular release related to this customer?Thanks for your help!
Hey Productboard team! As a team we would love to know who interacts with our roadmap so we didnt want to have the link public without capturing who visits it. So in order to gate it we build a landing page that captures an email and sends a private link the subscriber. However, anyone can share that private link after. Would be great if this was built in Productboard. Make users signup or provide an email before viewing the portal so we can capture this info somewhere.
Trying to integrate custom date fields from JIRA to Productboard, in the past I was able to integrate JIRA date fields to Productboard text fields, now the only option is to sync it with Timeframe, if that is the only option, how can I make sure it is synced only one way? (Only from JIRA to Productboard)?
Is anyone tracking "sold commitments" to customers at the feature level and using this to prioritize their backlog?
SaaS companies who are scaling up may get bigger clients by selling features in contracts. These are hard to track as a normal insight in productboard since they carry more weight and have a date associated with them.It would be nice to:Have the “sold commitment” field add weight to the feature impact score Be able to visualize all the customers, their sold features and their commitment dates on a board.Anyone else dealing with this? If so, how are you doing it?
Hi all,I’m ingesting forum feedback from places like Gartner Peer Insights into the extention, and then setting the insights as coming from ‘Forum User’. However, when I assign these insights to a feature, it only says 1 person is talking about that features because it’s all captured under ‘Forum User’.Is this the best way to do it? Is there a way to show all feedback against a feature if its from one user? (One user as far as Productboard knows)Thanks
Hello everyone,We are starting to use Insights tab of Productboard to centralize and analyze the qualitative feedback and data we collect in multiple areas of our organization.We would like to hear any advice or pro-tips about how to implement Insights in a global B2C product.The intake process in particular: Triaging notes, processing and closing the feedback loop with contributors.What worked? What failed? Interested in both the process as well as the governance around it (documentation, change management, training etc). Thanks
Hi there,we are looking for a possibility to synch the RELEASE from Productboard to a specific sprint in the jira backlog. In Productboard is no field “sprint” and the only similar option is “release”. This field usually maps with “fix version” in jira, but not every project or product has a fix version. It would be ideal if this field could map with a sprint in jira.F.e. in Productboard the release is “S 12, 19.01.”Means, the ticket is for sprint 12 which is already scheduled in jira:However, the ticket would only be mapped to a fix version, but a fix version in jira is also not really connected to a sprint. Has anyone an idea how a ticket could be added to an existing sprint in jira without our PO is doing it manually? And vice versa, if a ticket is not ready for deployment and will be removed out of the current sprints and moves to the following one, this should be reflected in product board. Another question would be, how a ticket could be added to a sprint which is not created yet
Hi all,I’m a new Productboard user, and I’m having trouble visualizing something on our feature timeline roadmap. Here’s my issue:We have a main feature, let’s call it Feature A Based on feedback we have received from customers (and categorized in Productboard!), this feature has 3 subfeatures: A1, A2, and A3 We have decided to spend time working on Feature A from Feb 1 to March 1. I have added Feature A to our feature timeline roadmap for those dates HOWEVER -- During that period, we only plan to work on subfeatures A1 and A2. Subfeature A3 will NOT be worked on After working on something other things for a while, we plan to return to Feature A in June, and will work on A3 at that time.What is the best way to show this plan on our feature roadmap? I don’t think I’m able to add Feature A to the roadmap more than once, nor am I able to add subfeatures directly to the roadmap.Thanks,Michael
There was another thread asking for this but I felt the need to reiterate this request.Tables are instrumental with how myself and other Product Managers use Jira. They allow for scannable requirements that don’t span the entire description, and are not easily replaced by bullet points.Not having table markdown support is a limiting factor in how we gain value from PB. I hope you can use this request as an insight for that feature :)
Hi community,In some of PB video I’ve noticed beautiful custom prioritization columns:How to create such? I couldn’t find the way. T-shirt effort estimate (how to create such custom scoring?) Yes/No checkbox column (“UX Required” in the screenshot) - how to create this? Thanks!
Hey there,Is anyone out there using Productboard together with John Cutler’s North Star Framework? We have identified a North Star Metric, a number of Inputs and relating Metrics. I’m finding two things a bit lacking:First, I don’t really see a great way to keep all this related. The Objectives capability in Productboard is OK, but with only a flat list of objectives (with themes) it seems to miss on the relationships. The second thing is in general there doesn’t seem to be a super easy way to incorporate metric goals for a given initiative / opportunity / bet in Productboard. I could do something like a custom Number field but given more than one initiative / opportunity / bet can relate to a metric I feel like it would be hard to keep up with. A related entity of metric would be helpful.Is anyone hacking up ways to make this work? How are you doing it?Thanks,Spencer
Hello community,We’re considering using PB. We’re heavily on Azure DevOps. I’m curious where can I read about 2-way sync between PB and Azure DevOps: I created user-story in the ADO, will it automatically appear in PB? I created feature in PB will it automatically appear in ADO? Where can I read more about PB ↔ ADO integration possibilities?Thanks,Best Regards,Oleksandr
Hi all - I actually interested in meeting Productboard users because I would like to use an extension of Productboard for marketing and customer education.Our product team is already looking to use some elements of the product, but I would like to build a customized configuration of the portal - I have shared it with about fifteen people at my organization and it is by far one of the most advanced content frameworks beautifully designed. My compliments to the team! Beyond product feedback, I would like to use it to display use cases, and retain the same structure. Is anyone else using Productboard for public-facing lead generation? A few things any marketer worth their salt should love about Productboard:Each card is a page in Google, with a new unique URL. (see bottom left) The options for collecting information are unbelievably remarkable, especially for when a sales rep reaches out Broader categorization is quite meaningful. In a draft portal I sent to my product team, across the t
Hello,One of the pain points I am facing is not having mandatory fields for features and notes. I can understand the logic behind notes as we want to make them easy to submit but what about the features? We already have fields and not having the option to make them mandatory is making us do admin work. Do you have any workarounds or best practices for this?
Hi All,We are trying to re-arrange our Productboard content due to recent Product reorg, due to such, we need to delete old objectives, tasks, drivers, etc. Is there a way to bulk archive/delete them instead of doing it one by one?In addition we are trying to restructured the feature organization board, move what was previously set as a Product or component under a newly set Products, currently there is no option for drug&drop, only archiving (for components onwards ), which is not our option of choice , since we can’t save the insights or notes and can’t access the feature themselves for reviewAppreciate any best practice suggestion
I had a couple folks reach out over private message after reading @Amir_Rozenberg’s Medium article that we posted yesterday (read the post here), asking how I’ve approached continuous discovery using Productboard. In the interest of transparency, here’s an approach that I’ve followed in my past product work:Use Objectives to capture the Desired Outcome (in OST). Alternatively you could also use a Component as you organize your thoughts then move these over to Objectives once you’ve settled on the priorities. You can’t track different levels of Objectives easily in Productboard -- most teams focus here on the product’s objectives Use Components to capture the Opportunities (in OST). These can be nested if needed Use Features to capture Solutions (in OST) Create insights from notes and add to Components so you can track and identify the Opportunities most important to your customers. The User Impact Score can identify those for you. Use Segmentation to narrow in on those Components most
Hello !We are releasing some clients, but not all of them at the same time, we have like two waves. We would release part of our clients one day, and then one week later, we would release to all of our clients. So we would love to have a customized status for releases, to clearly state if it’s release to everybody, or only part of our clients. Is that possible ?Thank you for your help !
Hey folks,The prevailing type of customer feedback we are receiving are feature requests. Most of these feature requests are straightforward - requesting something we have on our roadmap in a few quarters. I would love stakeholders to be able to directly “upvote” future planned features and submit relevant customer insights that would allow us to build them right.With Productboard I couldn’t find a way to do that - PMs always have to be in the middle “processing” the insights. I believe there’s a way to easily remove 50% of maintenance work for PMs if there’s an easy way for stakeholders to submit feature requests directly. I don’t believe PMs always need to be the middlemen for processing insights.How do you decentralize your feedback process? With Jira Product Discovery there’s a way for stakeholders (non-makers) to directly submit insights, which I find very helpful. Due to this simple difference I’m seriously considering switching to Jira Product Discovery.
Issue:Post Integration + Web Hook Set UpHow do I … manage/filter notifications related to a Specific Product/Feature? (Swimlane on Roadmap)To... a Product Specific Slack Channel. I’ve managed to link the Slack channel using the Article below, but I’m concerned it may flow ALL updates company wide to 1 channel. This article shows how to set up the integration but I can’t find information about how to USE the integration post-set up. Article: https://support.productboard.com/hc/en-us/articles/360056319354-Track-workspace-updates-using-a-Slack-notification-feed
Create an account
You can create an account below using either single sign-on or a username/password. Already have an account? Login.
Join or Login
No account? Create an account
Single sign-onEmployee login Log in with Productboard
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.