Funny I too have been wishing I could see that here in Fibery! You and I were chatting about tasks getting “stale” and I was just thinking about this in my work in Fibery today:
This is a great way to get more insight into that. This ties into a big hope of mine that when Automations come around, you’ll be able to affect Date fields by moving status, and thus get even more insight into execution and how long you are in a particular status.
This is something that I saw amazingly well implemented in TargetProcess (sadly you can’t get a free account any more to see some of this stuff). I think if I remember correctly it worked like this:
- you set a ‘planned start date’ and ‘planned due date’ - what you might regularly do as a “date range” in something like ClickUp
- when you moved the status to a defined “in progress” state - and TP had a great multi-faceted Workflow that I hope gets to Fibery one day too, @mdubakov really tempted me about that here (have you seen @Oshyan?):
- then, a “date started” field was filled in automatically. So now you can see how long it took for you actually start when when you thought you’d start.
- when you move to a “completed” status, another date field called “actual completion date” fills in.
So then you can do cool stuff like:
- compare planned to actual start date
- compare planned to actual completion date
- look at planned start date and actual completion date to see how well you did on execution in the larger picture: when you actually got to something you planned, and when you finished it, vs. when you thought you’d start & finish.
So this is the type of stuff I am really dreaming of in Fibery since it was so well done in TargetProcess. And “time an entity sits in a status” is a big element of that.
Hope that was useful follow-on! And very glad you posted this request!