I often find that I break and then have to fix new goals because my default deadline is in the morning, so changing the deadline puts the initial dummy data after the current date according to goal logic. So after creating a goal and then changing its deadline, I often have to go back and edit the dummy datapoint to fix the goal. It would be a lot more straightforward if the deadline was presented as an option during goal creation, and I think it would also add value by reminding people what their default deadline is and prompting them to change it if it makes sense.
Here’s what it looks like when I break the goal this way:
Ooh, thank you! We’ve been fixing a couple things that sound adjacent to this but, um, clearly not well enough.
To clarify, you’re saying that including deadline in goal creation would allow for better working around this bug? I think I agree because we want deadline to be part of goal creation anyway.
We also want to fix the root problem, of course. Maybe that’s easier said than done. Or maybe it’s as simple as nixing this “all datapoints are in the future” error.
Hm. This is surprising to me. I’ve fixed several things around making restarts and new goals deadline aware recently, and I wasn’t able to reproduce this when I tried making a goal after an earlybird deadline like this.
can we defectus this up with steps to reproduce? here’s what I did that I thought would reproduce and did not…
Aha! I’ve reproduced it! Let me edit in a missing step from your reseminata [done; amended step 1]. Also @bee, it turns out, accidentally missed your step 3 when she tried to reproduce it. (Having it laid out as numbered steps definitely helps; thank you again!)
So, I think we can just suppress this error and be on our merry way! It looks slightly weird after the deadline shift:
That black triangle is because “today” is now before the start of the bright red line, ie, Beeminder doesn’t know how to color it because it’s not on either side of the red line.