i feel the feature-requests portal is not as timel...
# random
b
i feel the feature-requests portal is not as timely updated as compared to putting up Github issues that are labelled as feature requests, which can link to specific PRs and more easily linked to other issues
i
Thanks for the feedback xL! cc @little-megabyte-1074 & @astonishing-answer-96712
b
its just an observation that I've never seen any Github PR that addresses any feature request in the portal. Seems to be a retrospective action
On the plus side, there is a nice roadmap feature on the portal
a
Hi xL! Thanks for the feedback, are there any issues in particular that you really want to see prioritized on the roadmap? We’ll talk internally and get some of these issues sized.
And are you saying you’d like to move away from the portal altogether in favor of using only Git?
b
I'll love for the social collaboration to move forward (John and Maggie might still recall that conversation :) ) It's just that I felt that there is a disconnect between requests and PRs by using the portal, hence I'm wondering if git is a better solution.
l
Hey @better-orange-49102!! Thanks so much for the feedback - you’re definitely right, we’ve dropped the ball on keeping the feature request portal in parity with what we’ve released. @astonishing-answer-96712 and I are going to put a bit more structure around how we manage the portal to keep it as up to date as possible; I’d love to revisit the conversation early next year to see if there are still issues! For the sake of transparency, I’ll share my high-level thoughts here I’m a bit hesitant to revert back to GH Issues for a few reasons: • It can be really tough to parse through requests vs. bugs • GH notification noise can be really overwhelming for folks & feature review/progress can get lost in the mix • Not all of our DataHub community members are used to working in GitHub & it can be a really daunting UX to share feedback/upvote Some of the benefits of the feature request portal are: • When creating a new feature request, end-users are prompted with “similar” requests which has been incredibly helpful for us to streamline common themes & minimize redundant requests • From a request management standpoint, the portal provides weekly updates to us to understand hotspots/activity - it’s super useful!! • The Roadmap feature allows us to tie upcoming initiatives to specific requests
its just an observation that I’ve never seen any Github PR that addresses any feature request in the portal. Seems to be a retrospective action
This is totally valid!! You’re absolutely right - historically, we’ve been updating the portal after the fact & linking out to release notes once the release it cut; here’s an example of a closed request with a link to release notes. I’m curious if there’s a way for us to streamline linking specific requests to PRs.. I’ll look into this one for ya 🙂