I have sent this to the Ninja's already, but I just wanted to see if anybody else could repeat this behaviour, or if perhaps this is the way OF is designed to run.
I think I have discovered a bug in setting a recurring project complete. If the project is overdue, I attempt to set the complete date to a date in the past (I simply forgot to check off the main project) using the inspector. The project then stays in the active list, still with an overdue mark on it; however, it does seem to respawn the project appropriately but doesn't seem to mark the current instance as complete. I have attached a screenshot showing what happens after I had attempted to mark the project "Weekly Cleaning" complete a couple of times (after thinking that it didn't work the first time).
So, is this a 'bug' or a 'feature'. It certainly didn't behave the way I was expecting it to.
I think I have discovered a bug in setting a recurring project complete. If the project is overdue, I attempt to set the complete date to a date in the past (I simply forgot to check off the main project) using the inspector. The project then stays in the active list, still with an overdue mark on it; however, it does seem to respawn the project appropriately but doesn't seem to mark the current instance as complete. I have attached a screenshot showing what happens after I had attempted to mark the project "Weekly Cleaning" complete a couple of times (after thinking that it didn't work the first time).
So, is this a 'bug' or a 'feature'. It certainly didn't behave the way I was expecting it to.
Threaded Mode