Now that I’m running Bike as a daily log of sorts, I find myself wishing tasks also supported a canceled state. I could add a canceled attribute but I feel that kind of clutters up the very mininal setup I have going on and doesn’t really surface at a glance. Any chance we could persuade you to add that?
I’ve found myself wanting an “in-progress” state.
I thought about this a little when adding badges, but couldn’t decide how to model it. Seems like the “correct” way would be to use a status attribute with options for something like:
- done
- in-progress
- canceled
- etc
The problem with that is we are already modeling done=date. I’m not 100% against changing that existing model to get things right… but I would want to make sure the new design is right for the longer term.
What do you think?
3 Likes
For me personally done=date doesn’t really mean much. If I wanted to track how long a task took, then I’d also need start=date and in-progress=time for that to become useful, and I think there’s plenty of other dedicated tools on the market that do that with buckets, tags, visualisations and other goodies attached. I like to keep it simple in Bike, I just need an at-a-glance overlook at what task status is. Therefore a @status attribute is plenty for me. I’m not sure how to reconcile that with people that do track their done dates other than to have information doubling (@staus=canceled and @done=date).