Comments (9)

Hi Krishna,
thanks for your feedback! We are trying to provide a simple yet powerful tool for project planning. This means that we are trying to avoid having too complex functions for holidays and vacations etc. We understand the need of taking weekends into account, but also see it as a first step towards a complexity that we do not want to introduce. Right now this is where we draw the line when it comes to scheduling complexity. Further in the future we might reconsider depending on for example user demands.
Best regards

Hej Silvija, I do understand your answer and highly appreciate the importance of simplicity. However, this is an issue that really hurts and almost prevents the tool from being used professionally (from my perspective!). If I need to consider weekends manually in a large project - that means a 1-day process starting on a Friday needs to be assigned 3 days so it is due on Monday, and so on - and experience rescheduling need (as in all real-life projects) then all those artificial manipulations render the planning senseless.
Maybe multi-religious holidays are a step to far, but weekends? Please reconsider!

This really prevents me from using this software as a project planning tool. For me, the Gantt chart is totally unusable. In the Gantt chart it shows, that we are finished with the tasks on time, where in reality, it would be finished weeks later, because of weekends or part time employees.

Same comment above excluding weekends is a basic feature not a slippery slope. I totally undertsand your view on keeping it simple but for me this is about making it usable for planning.
It makes using a Gantt very difficult as for short activities you have to change the period depending on the start date. It is very easy for people to forget when moving dependencies.

DIMELO - social media platform editor