Numbering in ::task
-
I can't understand the numbering of tasks in ::task. It seems that it preserves the original order tasks were added. What the idea behind this? Shouldn't be better numbering it like a multilevel list?
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
-
I can't understand the numbering of tasks in ::task. It seems that it preserves the original order tasks were added. What the idea behind this? Shouldn't be better numbering it like a multilevel list?
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
Each task gets its own ID, which are assigned in increasing sequence. This way you can easily refer to task, also by URL. When you drag&drop task in hierarchy the ID doesn't change, so it always refer to the right task. Also, if that distracts you, you can change column template in your view to not display the ID in the grid.
-
Each task gets its own ID, which are assigned in increasing sequence. This way you can easily refer to task, also by URL. When you drag&drop task in hierarchy the ID doesn't change, so it always refer to the right task. Also, if that distracts you, you can change column template in your view to not display the ID in the grid.
Good idea! Thanks...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
