#645
- Created on2008-02-20 12:59
- Reported by
- StatusFixed
- PriorityHigh (2)
- Assigned to
- Milestone
- Plan Level-
- Due Date-
add 'Done' state to contexts
When a context becomes irrelevant, you can either delete it or hide it. I'd like to keep the context for archive / statistics or for re-use if it becomes relevant again.
So deleting a context is not a good option, especially because all related actions will be deleted too. Therefore I currently hide all contexts that are 'done'. But some contexts like someday/maybe are hidden too. This gets confusing when you have a lot of hidden contexts
So I propose a separate state for contexts: 'Done' which acts just like 'Done' for projects. You can hide it from view, but seperate it from hidden contexts.
So deleting a context is not a good option, especially because all related actions will be deleted too. Therefore I currently hide all contexts that are 'done'. But some contexts like someday/maybe are hidden too. This gets confusing when you have a lot of hidden contexts
So I propose a separate state for contexts: 'Done' which acts just like 'Done' for projects. You can hide it from view, but seperate it from hidden contexts.
Leave a comment
on 2009-04-07 22:43 *
By lrbalt
Type set to enhancement
Severity set to normal
Resolution set to
Keywords set to
Version set to
Assigned to changed from Anonymous to lrbalt
Type set to enhancement
Severity set to normal
Resolution set to
Keywords set to
Version set to
Assigned to changed from Anonymous to lrbalt
How can a context be 'dropped' or 'closed'? The physical location or the logical context still exists, even if you don't have actions for it. 'Hidden' is the proper name, however, if, as the submitted suggested, you want to have several categories for hiding a context, then I would suggest 'inactive' as another one.
However, this raises the question whether you should:
However, this raises the question whether you should:
- see inactive contexts in the autocomplete function and
- be able to use them via REST
hidden is to put it out of sight, for example for someday/maybe stuff
if you use a meeting for a contexts and in time you quit going to that meeting, the contexts becomes inactive. You can hide the context or delete the context now. But deleting it will also delete all (completed) todos from Tracks. If you are not fine with that (i.e. keep your stats) you'd like to mark it inactive, dropped or closed (whatever term is best) so you do not see it anymore in dropdown lists, etc.
if you use a meeting for a contexts and in time you quit going to that meeting, the contexts becomes inactive. You can hide the context or delete the context now. But deleting it will also delete all (completed) todos from Tracks. If you are not fine with that (i.e. keep your stats) you'd like to mark it inactive, dropped or closed (whatever term is best) so you do not see it anymore in dropdown lists, etc.
For me it looks quite strange to have closed contexts. Does this really follow gtd? Maybe sometimes it's better to use projects.
But I understand the problem, that people like to keep their stats. So why not simply add a deleted state to contexts? This way they can act as removed in the app and only be visible in the stats.
But I understand the problem, that people like to keep their stats. So why not simply add a deleted state to contexts? This way they can act as removed in the app and only be visible in the stats.
on 2013-03-01 18:24 *
By lrbalt
Assigned to set to lrbalt
Status changed from New to Fixed
Assigned to set to lrbalt
Status changed from New to Fixed
(In tracks-tickets:65c0b867f66bb12481c79012160a86ce12136e16) add ui for changing state of context to closed. This fixes #645
Branch: context_closed_state
Branch: context_closed_state
(In tracks-tickets:4df340bd7b246277da5ee4256deff74fd3fd4873) add ui for changing state of context to closed. This fixes #645
Branch: master
Branch: master