This page is for Stockler's building a ticketing database, it explains the mandatory fields and gives good practices on other fields.
In tickets tables, dedicated formula properties must be used to delimitate sections and must be identified with these icons: ⏬ (Chevrons Down) for sections and ↪️ (Square arrow uturn right square) for “sub-sections”
e.g. section for inputs, section for outputs, section for computation
e.g. ‣,
-- Outputs --
- Illustration
Properties “case rules”:
🤓 Fields useful for a creator or a reader of a Ticket / Task should be in Words Like This (words with capital letters separated by spaces)
All those fields must be present in all ticketing system.
Title
Severity
Assignee
Status
Reminder:
Followers
Created by
Updated at
Created at
<aside> ⚠️ Sanity checks must not be done through views: it is hard to understand why the ticket is invalid, and adding a check requires updating all views.
</aside>
Sanity checks must respect the following principles:
Classical Sanity Checks should include (valid for all Tickets & Tasks)