2.1.0

Highlights

• Auto-archive: Completed tasks move into the project's archive on their own after a number of days you choose, set once for every project or overridden by a project in its own settings, and the archive completed tasks command does the same sweep right away.
• Inherited custom fields: Custom fields can be defined once for the whole vault or on a parent project, and every project underneath starts with them. Each project can still rename, retype, or hide a field it inherits, and a field it already had of its own can be merged into the inherited one, values and all.

Added

• Completed tasks move to the project's archive after the number of days set in the new auto-archive setting (#204)
• A project can override the auto-archive window in the project settings
• The archive completed tasks command moves finished tasks into the archive right away
• A sub-project has the custom fields its parent project defines (#255)
• Custom fields can be defined for the whole vault, so every project starts with them
• A project can rename, retype, or hide a custom field it inherits, in the project settings
• A custom field that duplicates an inherited one can be merged into it, values and all

Fixed

• Renaming a project from its settings page left its note and folder named after the old title
• A view failed to load when a note's properties held an invalid value for team members, assignees, tags, or dependencies (#252)
• A sub-project or subtask nested two levels deep drew a leftover connector line beside it when its parent was the last of its siblings