@thewallfishgtd

Hello,

Do you mean that the tasks you added to the project should inherit the project's attributes?

If so, how can we guarantee that all the tasks under the project can be done in the same conditions as the project's? For example, a project has a context "Office", but the tasks under it may have another context like "Errands". If it inherits the project's context "Office", you also have to edit the task first. Do you think it is more convenient?

Thank you fro your feedback and support.

Hi,

thanks for your answer.

I think there is no proper answer, it really depends on users usecases.

As far as I am concerned, I usually do the following:
- create a task, sets the context and date
- then a bit later, realize that it is made of several subtasks
- so add the subtasks, and click on task -> project conversion
- then I have to set the context and the date of all the newly created tasks : MOST of them have the same context and date, so I prefer to have inheritance of attributes and modify the few tasks that differ, instead of modifying all the tasks.

Of course, if it were possible to perform a bulk attribute edit, that wouldnt be a question : I'd use such a feature, which doesn't assume any prefered typical use cases and allows anyone to quickly set the context, date, etc. of the newly created tasks.

Best regards,
Eric

@thewallfishgtd

The subtasks (which will turn to tasks when you convert the task to a project) could inherit the attributes that the task has before it gets converted into a project?

Could you please tell me which version you are using now? Now, on the web version or the desktop app (Windows & Mac), you can perform a bulk edit on Start time, project, context and Goal. Here is a video on the web version that tells you how to do it. http://enblog.doit.im/post/56958636483/doit-im-tip-on-web-two-ways-to-change-start-time

Thanks for your support.

Hi,

> The subtasks (which will turn to tasks when you convert the task to a project) could inherit the attributes that the task has before it gets converted into a project?

yes, exactly.

I am using the web version. I am aware of the drag and drop bulk edit but that doesnt allow me to change several attributes at the same time:
- I select multiple tasks (e.g. in today)
- drag them to a different time (ex: tomorrow)
- then I have to change to the new time focus (eg. tomorrow)
- I have to find the tasks again, select them
- drag them to a specific context
- etc for all the other attributes

Inheriting the attributes at the time of subtask to task transfrom would solve this problem. A multi-attribute bulk edit would also do that.

cheers
eric

@thewallfishgtd

You can perform a bulk drag-and-drop operation directly on the view page of the project converted form a task. Thus, there is no need to switch between boxes.

On the view page of the project, change the start time of multiple tasks by the drag-and-drop operation. Choose "Group by Start time" in the project, and then you will immediately see the tomorrow's tasks.

In the same way, after changing the context, you can choose "Group by Context" and then you will also find tasks under the context you need with ease.

If there is anything else that we can help with, please do not hesitate to contact us.

Thank you for your feedback.

@michelle1987

Hi,
i disagree with finding with ease. If I have hundreds of tasks in Next, then when my newly created tasks are dragged to "Next", I'll have a hard time finding them, in order to select them and apply them a context.
As a user experience design, there is undoubtly a major flow here.

This app is still very useful, of course ! I'd quit otherwise. But there is also room for improvement.
Best
Eric

@thewallfishgtd

You may try the search feature to find the task. The search feature is supported on all the platforms we support. For example, on the web version, enter some key words in the search box at upper right and return to find the task you need. You can implement current search or global search. It's up to you. :)

And we will also consider your suggestion.

Thank you for your support.

Sure, i knew this. I just meant this is a very suboptimal user experience.
(btw i am a software engineer with experience in UX - which doesnt mean i am right, but it is an educated thought)

Sure, i knew this. I just meant this is a very suboptimal user experience.
(btw i am a software engineer with experience in UX - which doesnt mean i am right, but it is an educated thought)

@thewallfishgtd

We will think about it then. Thanks for your support on Doit.im.

If there is anything else that we can help with, please do not hesitate to let us know.