one to create common data like Status, coverage, priority, devices, browser version etc.,
Two - Product or project specific data like features, which might get updated more frequently.
The idea to have two sub-pages is to separate common data from project specific data.
Now start creating tables for each of the required details like status, feature etc.
Start creating the master data or the core data for your project need.
Based on the need you can have multiple master data, in this example one for Test charter and another one for Bugs.
💡 Pro-tip : Give proper names to table , it is essential to lookup these table later stages.
Interaction Layer
Once the core data tables are set, build an interaction layer to create, update and delete data. Don’t interact directly with the Data layer. Coda provides view of the data table.
Create a bug update view the data table “Bugs”
To keep away the distractions, make only the necessary columns viewable.
Try Details view , if that is helpful for your need.
Add a button “ Add bugs” to add new bugs. This can also be done by directly add a row option. But a button looks more elegant.
💡 Pro-Tip : User various filter and sorting options to filter out the data that is relevant. Example by applying filter it by currentuser() will display when assignee is logged in user.
Presentation Layer
Start creating views of the necessary master data and start building charts.
User formula any where on the doc to generate dynamic data.