johannesjo / super-productivity

Super Productivity is an advanced todo list app with integrated Timeboxing and time tracking capabilities. It also comes with integrations for Jira, Gitlab, GitHub and Open Project.
http://super-productivity.com
MIT License
8.67k stars 753 forks source link

Entering the Default Estimate during First use of Repeat screen, does not show it in Task list screen #3101

Open gitraghuram opened 3 months ago

gitraghuram commented 3 months ago

Your Environment

Expected Behavior

Add a new task. Click on the icon to see Additional Info pane. Click on Repeat In the screen that comes up, enter some value for Default Estimate. Click Save. Back in the Task List screen, it should show the estimate against this new task. For example, - / 1h 30m

Current Behavior

With the steps listed above, It does not show the estimate for the Task in the Tasks list. It is blank at the right-end of the Task. Even restarting the app still does not show the estimate in the Task list screen against this new task. (If you run this task at this stage, it does not warn at the end of default estimated time).

Click on Repeat again for that task. The Repeat screen shows the previously entered value of Default Estimate. Now change the value entered in Default Estimate Now it asks whether the change should be applied to All instances. Click to apply to all instances. Now the task shows, for example - / 1h 45m

But, after creating a new task, click the Repeat and then just save, and then go back to the Repeat screen and enter the Default Estimate. This time it (after asking whether to apply to all instances) shows the Default Estimate against the Task in the Task list. I guess it does not apply the Default Estimate (and may be other fields too) at the fist use of Repeat screen. It may be assuming that the user would enter only the Repeat Day/week etc information during first use. This need not be the case though. It is just a screen with multiple fields, and all of them should be applied to the instance.

Steps to Reproduce (for bugs)

1. 2. 3. 4.

Can you reproduce this reliably?

Able to reproduce reliably. May be I don't understand how i am supposed to do, but what i did above was based on my intuition.

Console Output

Error Log (Desktop only)

github-actions[bot] commented 3 months ago

Thank you very much for opening up this issue! I am currently a bit overwhelmed by the many requests that arrive each week, so please forgive me, if I fail to respond personally. I am still very likely to at least skim read your request and I'll probably try to fix all (real) bugs if possible and I will likely review every single PR being made (please, give me a heads up if you intent to do so) and I will try to work on popular requests (please upvote via thumbs up on the original issue) whenever possible, but trying to respond to every single issue over the last years has been kind of draining and I need to adjust my approach for this project to remain fun for me and to make any progress with actually coding new stuff. Thanks for your understanding!

github-actions[bot] commented 3 months ago

Hello there gitraghuram! πŸ‘‹

Thank you and congratulations πŸŽ‰ for opening your very first issue in this project! πŸ’–

In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. πŸ‘€

For more open ended discussions and/or specific questions, please visit the discussions page. πŸ’–

Jagdfalke commented 3 months ago

I can confirm this behaviour with the current version 8.0.1. The default estimate is not applied to the task.