You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For those of us who use lists to organize projects, it might be nice to be able to "archive" a list – delete the list but retain the tasks. There are a few different way this could be accomplished.
By moving tasks to an Archive list
Procedure
Tag all tasks in the list with the list name (e.g. tasks in Shopping list get #archived and #Shopping-list tags)
Move all tasks (completed and not) in the list to a target list
Delete the original list
Options
The following may be good candidates for user preferences:
Default target list (e.g. Archive)
Archived tag to mark everything that has been archived regardless of list (e.g. #archived)
Choose whether tasks with the archive tag should be hidden in workflow searches
And options available during for each archive operation
Target list to select something other than the default
Archive complete, incomplete, or both
By moving list to an Archive folder
Another approach to archiving a list is to create an Archive folder and simply move the archived list into that folder. This has some benefits and shortcomings compared to the above approach.
Procedure
Move list to the archive folder
Options
Select or create a folder for the archive
Choose whether tasks in the folder should be hidden in workflow searches
The second approach is simpler to implement and requires less configuration. It would be a simple one-click operation for the user to archive a list.
The first approach is more customizable. It reduces the total number of lists which may be important for people who use many lists with similar names (e.g. "Podcast 9/5/16" "Podcast 9/19/16"). It allows archival of groups of tasks like complete/incomplete while the second approach would operate only on an entire list.
If this concept appeals to you please respond with your preferred approach or any other ideas.
The text was updated successfully, but these errors were encountered:
For those of us who use lists to organize projects, it might be nice to be able to "archive" a list – delete the list but retain the tasks. There are a few different way this could be accomplished.
By moving tasks to an Archive list
Procedure
Options
The following may be good candidates for user preferences:
And options available during for each archive operation
By moving list to an Archive folder
Another approach to archiving a list is to create an Archive folder and simply move the archived list into that folder. This has some benefits and shortcomings compared to the above approach.
Procedure
Options
The second approach is simpler to implement and requires less configuration. It would be a simple one-click operation for the user to archive a list.
The first approach is more customizable. It reduces the total number of lists which may be important for people who use many lists with similar names (e.g. "Podcast 9/5/16" "Podcast 9/19/16"). It allows archival of groups of tasks like complete/incomplete while the second approach would operate only on an entire list.
If this concept appeals to you please respond with your preferred approach or any other ideas.
The text was updated successfully, but these errors were encountered: