How could we improve Flow?

Stop requiring a project for all tasks

Unfortunately, now that tasks always have a prefix of "Private Tasks" in the calendar view, the view has become very unreadable.

Also, the requirement to always have a project with each tasks slows down entering tasks significantly.

These changes should be reverted.

25 votes
Vote
Sign in
(thinking…)
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Oliver Breidenbach shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
not planned  ·  Shara responded  · 

I see what you’re saying – the project name (Private Task) listed with the task can look cluttered. The problem is that not including the project name can lead to confusion too. This is something we are not likely to change anytime soon but it does make sense to take a look at it in the future.

3 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...
  • Justen Holter commented  ·   ·  Flag as inappropriate

    Just dinged with this one, too. Not all tasks really belong to projects. Is this because the "inbox" has been removed?

  • Darlene commented  ·   ·  Flag as inappropriate

    I don't like it now that you can't add a task quickly without assigning a project and it's quirky

  • Heiko B. commented  ·   ·  Flag as inappropriate

    We have the same problem:
    - why do we require to choose a project for each Task???
    - We have a lot of tasks, which aren't project specific! It's circumstantial as well, to choose the "private tasks" project, for each task we are creating!
    - it isn’t a really good worakround to create the "private task" project and use this for each new task

    This is very cumbersome for us. Our productivity will decrease definitely.

    Could you change that asap!

Feedback and Knowledge Base