Convert item with subtasks into project


Not sure how much work or needed this feature might be, but figured I’d put in a request for it anyways.

The “problem” that I sometimes have (and this might be a personal workflow issue instead), is that sometimes an item with subtasks grows too big and I’d like to convert it into a project.

Now, while it currently supports dragging the item onto the Projects header and convert into a project, it still keeps the original subtasks listed in the project description, while in most likely case I’d intend to convert the subtasks into their own items, which I currently have to do manually.

So I was wondering if there was any possibility for that to happen automatically (maybe have a popup that asks if subtasks should be extracted or not, if any are found)

Curious to hear if this seems like something that could be beneficial for others as well

1 Like

It’s seems like a nice feature, and not difficult to add.
One challenge is to make it discoverable, yet unobtrusive. A pop-up is certainly not the way to go here. Maybe a button at project description level to convert description into sub-actions?

1 Like

Sure, a button would be good.
Guess it could either be shown normally in the project description (maybe only if it detects any subtasks to extract), or have it shown when editing the project description.
Not sure what would be most ideal

Gonna experiment with this. Thanks for the idea!

1 Like

This was easy enough. Released in 1.1.8 - Everdo Desktop Update 1.1.8- Everdo

1 Like

Oooh, I like it.
Cheers for the prompt implementation

This implementation works great. I like how when the subtasks that have been converted to actions still show as a progress bar when completed on the original project. Is there any way the original subtasks could be checked off when the action is completed? I can see it is still linked to the project since the progress bar is updated.

I thought I found a bug when converting subtasks on a project to actions but it looks like expected behavior and pretty neat too. The first subtask is shown in next, and when you complete then the second subtask is shown. And there I learned how parallel and sequential projects really worked.

Is there a way to convert a single subtask or subtasks not converted to tasks to tasks?

No, it’s not possible. The reason the original checklist remains untouched after the conversion is to avoid deleting user data without notice.

Do you mean convert a single checklist item? I think the only way is select the text, then press n, paste, enter

Thank you for your response. I can understand your rational and can respect that. The linking may be blurring more into project management but i don’t see checking a checkbox wouldn’t be be removing data.

I didn’t know about converting s single line into a task, thank you. Seems the more I read/use the program the more small and nice details like this I find.

Let’s consider one scenario.
We have 3 tasks but only two can be out next actions. The third is dependent on others.
GTD says, put this task into your project references materials and add to your next list when the time comes.

In Everdo it could look like that:
Add two next action items.
Add one checkbox item under the project description.
When the time comes, convert checkbox into a task in your next action list. But to in this scenario, the original checklist item should be removed. We need only an active action. Maybe there should be an option which tells Everdo how to behave when converting checkbox items? Whether delete original items or not.


Would be nice to have the option of deleting the original checklist, but I think manually deleting the checkbox it sufficient for now. The expectation is that this is used maybe once every few days, so saving 2 clicks is not worth it. In my experience, most of the time when I use the convert feature, I kill the original checklist container item anyway.