ForumsQuestions"Architectural" suggestion
"Architectural" suggestion
| Author | Message |
|---|---|
|
tommy.kelly |
Suggestion for simplifying and making more general some of the fields attached to a task.
Tag, Folder, Context and Status all seem to me to be unnecessarily specific examples of a more general idea. In effect they represent a key-value hash where you have hard-coded: a. The number of entries in the hash (four) b. The names of the keys ("Tag", "Folder", "Context", "Status") c. The data types of the values (strings for three of them, and then something a wee bit more complex for the "Status" key, since each string can also be above or below the line) d. The values permitted against the "Status" key Why not free the whole thing up? Allow the user as many entries as they want, let them call them what they want, and let them store whatever they want (within reason -- this is the least important addition I'm proposing) as values. Then they can slice/dice/sort/filter to their heart's content. |
|
Jake Toodledo Founder |
Thanks for the suggestion. We can't comment on a timeframe for implementation, but this is on our to-do list.
|
You cannot reply yet
U Back to topic home
R Post a reply
To participate in these forums, you must be signed in.