Hello JPD Team,
We are considering migrating to JPD, so we conducted an evaluation where we attempted to replicate our use cases in JPD. Currently, we use Jira to manage activities in our engineering, and for product management, we rely on Productboard (PB). We synchronize certain fields between them bi-directionally.
I believe this evaluation could be beneficial not only to the JPD team but also to the broader community.
Where JPD satisfies our needs:
- Ideas support custom fields, custom measures (e.g. RICE), Insights impact measure, labels, text formatting, custom templates (including tables), attachments (also in comments and insights), comments
- Solid change log for all important fields on ideas
- Various relation types between ideas
- Merging of ideas and support for bulk updates
- Creator and Contributor roles
- Integration capabilities with Slack, SFDC, Zendesk, Chrome extension
- Views and roadmaps over ideas are well-equipped – offering grouping, filtering, fields selection, sorting, organization in the menu, and cards on views
- Seamless integration with Jira
Where JPD should improve (not blockers):
- Creator role cannot manage fields (create custom fields, update field values)
- Multiple product support missing – solvable via a custom field
- Only basic support for Objectives and Drivers – basic needs solvable via Goals and custom fields
- Relations between ideas are not displayed on roadmaps
- Collecting feedback via a dedicated email address is not possible
- No build-in analytics (e.g. trending ideas last week/month etc.)
- Limited integration with Jira – fields synchronization capabilities; the recommended automation is not sufficient
Blockers for our migration:
- Feedback collection and processing capabilities are insufficient (the most significant blocker):
- Insight cannot exist without idea linked – creating insights first and linking them to ideas later is not feasible
- An insight is always part of one idea (like a comment). So if one feedback message contains multiple distinct ideas, it cannot be easily mapped to several ideas.
- Insights lack the ability to refer to customers that provided the feedback. So it is not possible to list all insights per customer (ideally with linked ideas and their statuses)
- No insights management exists – no way to list, search, update relations to ideas
- Only the person that created the insight or admin can update the insight. Creator role is not allowed to do so.
- No support for hierarchies of ideas. We are using wide and deep (almost 10 levels) hierarchy of categories over features/ideas. Easy navigation and search within the hierarchy are essential to us. The workaround using custom fields or some marketplace apps cannot match the seamless hierarchy support found in PB.
Regarding the blockers, the JPD team indicates they are aware and actively addressing them. Could you provide more insight into the solutions being developed and the anticipated timeline? Generally, we appreciate Atlassian products, so migrating to JPD would be a good step to us. However, the current blockers are preventing us from it. We plan to reassess JPD in November this year.
Thanks & Regards,
Michal
