Hi Ravikumar!
We group by Resources on our Scheduler implementation. Our resources represents areas and users. If an area has many users, there is no problem, as the design represents correctly:
But if one area and user are listed, the design becomes stretched, as seen on OP: