Thanks for taking the time trying out our product.
1.The product so far is in its early days. A better overview across projects will definitely be developed.
2. In the backend, a project is based on a template system. It's not visible to the user yet as this concept further needs adjustments before we can roll it out . In fact the current project design is just our first "plugin" of how a project can look. We hope to offer multiple ways to visualize a project in the future.
The state field is a system state (not changeable) that is used for triggers and in the future reporting. When you tick of a Task as finished, a trigger occurs that will look up the column with the system state "Completed" and move the task there. It's a bit rough at the moment, but could be a handy way to automate certain tasks later on and provide reports across projects.
Thanks for taking the time trying out our product.
1.The product so far is in its early days. A better overview across projects will definitely be developed. 2. In the backend, a project is based on a template system. It's not visible to the user yet as this concept further needs adjustments before we can roll it out . In fact the current project design is just our first "plugin" of how a project can look. We hope to offer multiple ways to visualize a project in the future.
The state field is a system state (not changeable) that is used for triggers and in the future reporting. When you tick of a Task as finished, a trigger occurs that will look up the column with the system state "Completed" and move the task there. It's a bit rough at the moment, but could be a handy way to automate certain tasks later on and provide reports across projects.