Data model

Each task is a unique entry in our database. Tasks can be of a certain template, perhaps your team uses “task”, “bug” or “idea”, fields for these types of tasks vary to allow you to capture data as needed without Flow having any opinions on how you should work.

For Flow to stay flexible and allow customisation with it’s fields, we have a concept called a “Task Model” - in the UI and in some of our docs we may interchangeably call these “Templates”. Each template has a series of fields which can be of a certain type. Under the hood, we store this data as a string array.

Tasks have an additional field called “metadata”, these are attributes of a task that are controlled from the UI, you’ll see that a task’s flagged status exists within it’s metadata, as does it’s estimation points.

Tasks may or may not have a status, in Flow a task is in the “backlog” if it does not have a status, statuses by default are controlled from the workflows section.