Today only requests have priority properties. When
tasks are created it would be nice if the priorities could
be set individually.
This applies to both orphan tasks and tasks which have
One could argue that the request already has a priority,
which the tasks then should relate to. However. I came
across a case where we had a request that ended up in
two tasks. One task was a quick-fix solution, and the
other task the final implementation. The quick-fix was a
high priority task, whereas the final implementation was
a low priority task. It seems unnatural to create an
extra request just to put the high-priority task into, and
I also feel that an orphan task would be wrong.
I believe that task priority properties would have made it
easier for me to be accurate in my orders to the
Log in to post a comment.