Krisp´s mockup... > Comment

Some comments / #4916

EditBookmarkDelete
Thanks for the sketch. I know that doing a sketch is far more difficult than just talking about features. But believe me: it was worth the effort because it makes your suggestions much clearer. Don't be afraid about colors and layout stuff. There are lot more people who can take care of those things...

General notes

  1. I think this is way too much information for a general user. At least of a projects overview (mind the plural). We are talking of several projects here. Probably 20 or 30! Imagine several pages long list.
  1. I would suggest to implement a similar overview for one project for printout. We could then implement a new feature "view details of selected projects" which would assemble all the details on a single html page for printing. (This would also be useful for documentation).

Some comments

  1. I like the coloring of the task bars
  2. Doing an graphical overview of the milestones is easy, but I personally doubt that this would have any benefit in daily life. I think this is like arguing about religion here. :) Everybody wants it different.
  3. Closed Milestones are just that: "Closed". It doesn't matter if there are any open tasks it there. If someone decides to close it, well. No problem. Actually in my daily work this happens quiet often, because some tasks are just not done. There are simply "ignored".
  4. Maybe we should not mess up "Status" and "Changes" of a project. I think both things are used in pretty different situations. If you discuss with upper management about project status, you only want status on you printout. Not changes or comments. Separating those tasks would simplify the interface.


Some questions

  1. Do you really need the project description? I mean... Really?
  2. Who writes your Status description?
  3. What is baseline meant for? For the first moment I would say that, if I don't understand it instantly, it is probably a too complex feature for streber: "keep it simple..."