# Feature Request Triage Process 1. GitHub Issue has been identified as a "Feature Request" and has the `Needs: Backlog review` 2. On a weekly basis the PM team triages the Backlog 3. PM + Eng Leads determine the following: 1. Determine if it fits within our Roadmap (link) 1. If it's not - we can nicely respond to the customer that this currently isn't in our roadmap and thank you for your submisson but we won't be addressing this request at this time. 2. If it aligns with our Roadmap, is well scoped, and doesn't require Design investigations we can recommend add the `help wanted` tag to indicate to the community that this feature request can be a contribution 3. If it aligns, and is not well scoped, and most likely needs PM or Design Investigations, we assign it to a PM add determine 1. If we can address this for next quarter - tag with `QNext` (figure out the tag) to indicate to that we intend to take this into consideration for planning our next quarter of work 2. If we can't address this for next quarter - tag with `Revist` (figure out the tag) to indicate that we will come back to this within 2 quarters to see if this is something that we should include in the next `QNext` 4. If it's aligns, is well scoped, and PM + Design Investigations are complete - We add it to our Monthly Iteration Plan (link) as a community feature request :::info Issues - [ ] 1: Do we want to manage everything with tags? - [ ] 2: Do we want to have specific Milestones that we put Issues in to help communicate things that are proposed for Qnext or in the "Icebox/Freezer"? ::: Next Steps - [ ] Need to finalize the process with @JustSlone - [ ] Determine if there are different types of Issues that we should include (should we only look at `Type: Feature` issues) - [ ] Schedule a weekly meeting to look through the `Needs: Backlog review` - [ ] Start scrubbing through the old issues - [ ] Start addressing the new issues coming in ## Patterns - Not in roadmap, we are not building new complex components right now - Not an issue for now, close and consider for future component work - Consider for next release - This is fixed??? - Dev follow up