FeatureEvery plan

Project settings, archiving, and deleting

Rename, rewrite the description, archive when it is finished, delete when it should never have existed.

By Updated

Both from the settings page, reached by the gear on the project header. The description is rich text, the same editor tasks use.

Once a project has a description there is a quicker route: the description button beside the project name opens it in a modal you can edit in place, without leaving the task list. Esc closes it. A project with no description yet is given one from settings.

If rewriting it is the part you keep putting off, the Project Description Writer drafts one from the project name and its tasks for a single To-Did, and you edit it before it saves.

Archive, almost always.

  • Archive takes a finished project out of your working views and keeps everything. It is restorable in one click from the archive, and its completed tasks stay in your history and your numbers.
  • Delete is permanent and takes the tasks with it. It is for the project you created by accident, not the one you finished.

Watch out

Deleting a project deletes its tasks, and that is not undoable. Archiving costs you nothing and is reversible, so if you are hesitating, archive.

The end-of-project move, and the one worth using instead of delete.

  1. Open the project and click the settings gear.

    Archive and Delete live together in a Danger zone at the very bottom of the page, deliberately away from the fields you edit, so nobody archives a project while reaching for Save.

    Open Projects
  2. Press Archive.

    The project leaves your working views immediately. Nothing is deleted: its completed tasks stay in your ToDid Log, your streaks and your reports.

  3. Find it again in the archive.

    Everything you have archived is listed there with Restore and Delete on each row. Restore is one click and puts it back where it was.

    Open the archive

Yes, to another workspace you own, from the workspace settings page. The tasks, subtasks and comments all come with it.

Dependencies that would end up spanning two workspaces are pruned in the move, because an edge across that boundary cannot mean anything. Blockers wholly inside the project survive.

Similar readings

Everything below is in the Happiness Center.

Was this article helpful?