Closed
Bug 274643
Opened 20 years ago
Closed 20 years ago
Marking tasks as completed from task sidebar does not publish change to remote server
Categories
(Calendar :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 239779
People
(Reporter: jdkeith, Assigned: mostafah)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 When checking the "completed" checkbox next to a task in the task sidebar, the change is not published to the server if the calendar is subscribed to. This occurs regardless of the setting of the calendar's "automatically publish your changes" checkbox. When starting the program again, all tasks that were marked as completed using this method return to their uncompleted state. There seems to be no problem marking tasks as completed via the edit selected task dialog. Reproducible: Always Steps to Reproduce: 1. Create and publish a calendar or subscribe to one for which you have write permissions. Make sure "automatically publish changes" checkbox is checked. 2. Create some tasks. 3. Mark them as complete by checking the checkboxes next to their names in the tasks sidebar. 4. Close and relaunch Sunbird. Actual Results: Any tasks that were marked as completed via the sidebar reverted to their state in the remote file. Any that were completed via the edit selected task dialog retained their state. Expected Results: Retained the state for tasks completed/uncompleted by both methods.
Thank you for the report. This has been reported in bug 239779, but that doesn't have "completed" in the title, making it hard to find. I will add it. *** This bug has been marked as a duplicate of 239779 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Comment 2•18 years ago
|
||
The bugspam monkeys have been set free and are feeding on Calendar :: General. Be afraid for your sanity!
QA Contact: gurganbl → general
You need to log in
before you can comment on or make changes to this bug.
Description
•