-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Task Does Not Remember Percent Complete or Priority On Status Change #2335
Comments
Thanks for the report. I can confirm that setting the status to Line 349 in 08a9ae1
I guess it is up to debate whether that makes sense, and I tend to agree with you that it might be better to not touch percent complete in that case. However, I cannot confirm that the priority would be affected by setting the status. Could you please double check that this is really the case for you and you didn't accidentally set it yourself or had another client change it? |
I've had the priority reset, and I've had it remember its value. Tonight, working with it further, the percent complete is always reset, but the priority remained. I cannot explain why in toggling the status the priority was reset. I will chock that up to a stray mouse movement. I tested further and if you choose complete, but then need to reopen, the percent complete is lost and set at I see the logic in the way it works, but on returning to in progress, the original percent complete should be restored. |
Unfortunately, this is not possible. We don't have a history of edits that one could go back to. We cannot do that for other values, and we cannot do it for the And if a task gets set to However, in #2365 I adjusted the logic in a way that setting the status to |
Couldn't you just stuff it into cookie or local browser variable? |
Steps to reproduce
Expected behaviour
When a task needs attention, the admin (or responsible party) addresses the issue and then returns the task to in process. The percent complete and priority of the task before the needs attention status was set should be restored.
Actual behaviour
After needs attention is set, and the issue addressed, returning the task to in process causes the percent complete to be reset to the beginning and priority to be reset to 1 (high) - this makes no sense and loses valuable information.
Server configuration
Operating system:
Running on Archlinux: 6.4.12-arch1-1
Web server:
Apache/2.4.57 (Unix) OpenSSL/3.1.2
Database:
mariadb 11.1.2-1
PHP version:
mod_fcgid/2.3.9 PHP/8.1.23
Nextcloud version: (see Nextcloud admin page)
Nextcloud Hub 5 (27.0.2)
Tasks version: (see Nextcloud apps page)
0.15.0
Updated from an older Nextcloud or fresh install:
Fresh install
Signing status:
No clue - cert by Let's Encrypt
List of activated apps:
Nextcloud configuration:
Are you using external storage, if yes which one: local/smb/sftp/...
no
Are you using encryption: yes/no
no
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
no
Client configuration
Browser:
Firefox 115.2esr
Operating system:
openSUSE Leap 15.4
CalDAV-clients:
none at the moment
Logs
Web server error log
Nothing relevant unless enabling APCu caching is attempted and then the following error occurs, even though APCu is shown as enabled in
php_info()
. APCu caching is currently disabled. See New Install 27.0.2 on PHP8.1 Archlinux, APCu fails, .well-known warnings for details.Nextcloud log (data/nextcloud.log)
Browser log
The text was updated successfully, but these errors were encountered: