🌊

Workflow

Website Requests
The Website Requests table is a list of backlog of requests open to anyone to monitor or use to make requests for the BDAO website. A request can be an enhancement idea, feature or page request, or a bug you found.
Why duplicate the effort between Notion and Github?
Github is not user friendly and requires an account to create issues.
What is the process?
  • Request is entered into table by anyone - status is set to New
  • PM/Team Triage requests weekly and either accepts the request or rejects it
    • If the request is accepted the status is set to Backlog, the issue is added to the Backlog in Github, the link is added to the website request table, the issue is placed in a development phase
    • If the request is rejected the team communicates the reasoning to the requestor, notes are updated with the reason and the status is set to Won't Do
  • Once the request is completed and released to production the request moves to Done
🌊

Workflow

Website Requests
The Website Requests table is a list of backlog of requests open to anyone to monitor or use to make requests for the BDAO website. A request can be an enhancement idea, feature or page request, or a bug you found.
Why duplicate the effort between Notion and Github?
Github is not user friendly and requires an account to create issues.
What is the process?
  • Request is entered into table by anyone - status is set to New
  • PM/Team Triage requests weekly and either accepts the request or rejects it
    • If the request is accepted the status is set to Backlog, the issue is added to the Backlog in Github, the link is added to the website request table, the issue is placed in a development phase
    • If the request is rejected the team communicates the reasoning to the requestor, notes are updated with the reason and the status is set to Won't Do
  • Once the request is completed and released to production the request moves to Done