Thanks for submitting this Idea and apologies for the very delayed response.
Can I understand a little bit more about this request?
I can appreciate the use case to Hide objects in the Model view however the intent of the Status update view is to not only change the status of some objects but also to see the existing status of other objects that are not being updated; the ability to hide the object in the Status update view seems to defeat that purpose.
Is it the case that when the user is presented with the objects associated with a Task in the Status update view that there are so many objects that some need to be hid in order to status the others?
If you can provide a bit more information concerning the use case for this it would be appreciated.
Hi Thomas,
Thanks for submitting this Idea and apologies for the very delayed response.
Can I understand a little bit more about this request?
I can appreciate the use case to Hide objects in the Model view however the intent of the Status update view is to not only change the status of some objects but also to see the existing status of other objects that are not being updated; the ability to hide the object in the Status update view seems to defeat that purpose.
Is it the case that when the user is presented with the objects associated with a Task in the Status update view that there are so many objects that some need to be hid in order to status the others?
If you can provide a bit more information concerning the use case for this it would be appreciated.
All the best,
Luke