Airtable Linked Records: Connect User Stories to Requirements
Link user stories to requirements in Airtable with a linked record field, and see the link appear on both sides: simple traceability for business analysts. Shown on a real Airtable base on the free plan.
Step by step
The link
- Linked records. A linked record field shows which user stories deliver which requirement, and it works in both directions. Here we link one story to one requirement.
- A link field. In the Requirements table, the User stories field links to records in another table, User Stories. Each grey chip in a cell is one linked story. The requirement Track my order has 2 chips, so it is delivered by 2 stories.
- Add a link. The requirement Keep a wish list has an empty User stories cell, so no story delivers it yet.
Link a story
- Add a link. Click that cell, then click the plus. Type wish in the search box and pick the story Save items to a wish list. It now shows as a grey chip in the cell.
- Expand it. Expand the Keep a wish list record. The linked story now shows as a card inside it. The card shows the story's own fields (As a, I want and So that), so you can read the story without leaving the requirement. Press Esc to close the expanded record.
Both sides
- Both sides. Now open the User Stories table from its tab. Airtable has filled in the Requirements field for Save items to a wish list on its own. The story now points back to Keep a wish list, and nobody typed anything on this side.
Recap
- Link once, see both ways. A linked record field connects 2 tables. Link once and both sides update. Use it for requirements and stories, risks and owners, or a full traceability matrix.
Common mistakes
- Typing story names into a text field. Plain text only looks like a link. Nothing appears in the other table, and a renamed story leaves old text behind. Use a linked record field, so each chip is the real record.
- Adding the link again on the other side. Airtable already adds the matching field in the other table, like Requirements in User Stories. A second link field you make yourself creates a separate link that can drift out of step.
- Picking the wrong record from the search. A search like wish can match several stories with similar names. Read the full name before you pick it, and expand the record to check the story's fields if you are unsure.
- Splitting one requirement into several rows. One link field cell can hold many records, like the 2 stories on Track my order. Keep one row per requirement and add every story that delivers it to the same cell.
When a business analyst uses this
Before a sprint review sign-off, a BA keeps requirements and user stories in one Airtable base and links each story to its requirement. Any requirement with an empty User stories cell, like Keep a wish list, is a gap to raise with the product owner before the backlog is agreed.
Questions people ask
How do you use linked records in Airtable?
Add a linked record field that points to another table. Then click a cell, click the plus, search for the record and pick it. The link shows in both tables.
Does a linked record show up in both tables?
Yes. When you link a requirement to a story, Airtable adds the link to the story's matching field too, so you only link once.
How do you count linked records in Airtable?
Add a Count field and point it at the link field. It shows how many records are linked in each row, so a requirement with no stories shows 0.
