Today during the development call @Symbioquine@Farmer-Ed@fosten and I talked about the challenge in modifying a log to show that the action the log represents will never happen as originally planned. We think it makes sense to add an abandoned status to logs that can be used to represent that a log will never be completed as specified. This allows the log to keep all of its metadata about the action that was originally planned to happen, without being modified or deleted. We thought “abandoned” is strongly worded (maybe too much?), but it’s also quite clear, and better than “closed” or “wont do”.
Current workarounds to represent this situation could be:
Delete the log and lose all evidence of the planned action (we want to keep the data!)
Keep log as planned - but this will appear in the Upcoming / Late tasks dashboard
Adding relevant notes to the log and marking as done to remove from dashboard
I’d say it belongs in the status field : abandoned.
It’s not done, and not pending any more, so I’d want it out of sight, but easy to pickup later.
And it seems natural to change this in the status field.
I think a flag draws unneeded attention to something you want out of the way.
That was more or less the discussion for a new option in the status field.
I’d agree that while keeping the log may be useful a flag would draw unnecessary attention to a log that would better ‘almost’ hidden.
@paul121 I think although a bit strong Abandoned is not an awful word, although the description ‘will never happen’ or ‘won’t do’ is probably not right either, it’s more ‘postponed indefinitely’ as there is always the chance an Abandoned log may be picked up later if circumstances change. Although I suppose in most circumstances if it runs into a new season then a new log may make more sense anyway.
“Abandoned” sounds good in Spanish. It suggests one has moved on without making a decision about it.
I like “abandoned” to flag an active task that somehow have lost importance over time and is still hanging at the bottom of the list because somehow the user doesn’t feel like deleting it.
A bulk action (as @mstenta suggested) could archives all those “abandoned” logs that fall in a specified period of time (“older than two months”; “older than a year”; etc.) to get them out of the list (as @pat suggested)
A query including key words matching those of the task could bring it up again (for example, for when there is money surplus and those old development ideas can be revived)