You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since each task represents a single measurement to be taken, it's plausible that large applications may have hundreds or even thousands of tasks. A simple list of tasks would not be sufficient for organizing and navigating through them.
Even for smaller numbers of tasks, tasks would benefit from a logical grouping (e.g. these tasks are for my application Foo, and those are for application Bar).
Some possible strategies off the top of my head:
Task groups. Alternative names: namespace, project.
Task tags.
Bonus: it should be designed to make way for a future more sophisticated permissions model (e.g. Alice is a developer for Foo, should only be able to manage Foo tasks).
Without this, we run the risk of people organizing by creating multiple Accounts, which may complicate billing.
The text was updated successfully, but these errors were encountered:
Since each task represents a single measurement to be taken, it's plausible that large applications may have hundreds or even thousands of tasks. A simple list of tasks would not be sufficient for organizing and navigating through them.
Even for smaller numbers of tasks, tasks would benefit from a logical grouping (e.g. these tasks are for my application Foo, and those are for application Bar).
Some possible strategies off the top of my head:
namespace
,project
.Bonus: it should be designed to make way for a future more sophisticated permissions model (e.g. Alice is a developer for Foo, should only be able to manage Foo tasks).
Without this, we run the risk of people organizing by creating multiple Accounts, which may complicate billing.
The text was updated successfully, but these errors were encountered: