Don't close V3 feature requests as complete via OG Redux
A feature being added to OG Redux is not a replacement for a feature being requested for V3.
Feature requests filed for V3 are being marked as complete when the feature ships in OG Redux. OG Redux having a feature does not remove the need for it in V3, which is intended to remain the primary experience going forward; requests tagged for V3 should stay open until the feature exists in V3 itself.
Log in to comment and vote
Comments1
Nov 10
PinnedThanks for flagging this. You’re right: “Complete” was the wrong status. A feature shipping in OG Redux doesn’t mean it exists in V3, and we shouldn’t have marked V3 requests as done because of it.
Here’s how we’ll handle this from now on:
Planned for V3: the request stays open until it ships in V3.
Not planned for V3: we close it as Not planned, not as Complete. If the feature already exists in OG Redux, we’ll mention it so you know where to find it today. That’s only a pointer, not a substitute.
We’d rather tell you upfront than leave requests open that we don’t plan to build. If our plans change, we’ll reopen them.
I’m closing this post because it’s feedback on how we run the board, not a feature request. The change above applies from today and I’ll backfill the history now.