::Task
-
Tasks status has an option called
new. It's something that shouldn't be choose by one who defines tasks but assigned to tasks that just created and has noassigneejet. From the point whenassegneeadded it should disappear (and no status changes with noassignee...) IMHO. -
Tasks status has an option called
new. It's something that shouldn't be choose by one who defines tasks but assigned to tasks that just created and has noassigneejet. From the point whenassegneeadded it should disappear (and no status changes with noassignee...) IMHO.Thanks for feedback. Indeed, some kind of workflow could add more value here. Not necessarily with the strict rules you've described (e.g. it should be possible to reject task, no matter whether it is assigned or not). Currently there is no logic maintaining things like this, so user can create any combination of tags. However, we have in our plans adding a layer on top of current system, so users can define e.g. that when task is closed all its child tasks are closed too, etc.
-
Thanks for feedback. Indeed, some kind of workflow could add more value here. Not necessarily with the strict rules you've described (e.g. it should be possible to reject task, no matter whether it is assigned or not). Currently there is no logic maintaining things like this, so user can create any combination of tags. However, we have in our plans adding a layer on top of current system, so users can define e.g. that when task is closed all its child tasks are closed too, etc.
Sound good - waiting to see :)
