Closed
Bug 697321
Opened 14 years ago
Closed 14 years ago
Warning required when saving a task lacking start or due dates
Categories
(Calendar :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: haroldtmunn, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20100101 Firefox/8.0
Build ID: 20111019081014
Steps to reproduce:
Click on any date, then type Ctrl-D. The New Task dialogue opens.
Enter details such as title, category, description etc., but omit start and due dates.
Click on Save and Close.
Actual results:
The dialogue box closes.
The task is not saved.
Expected results:
A warning dialogue should appear requiring the user to confirm abandoning the new Task and warning the user that the Task will not be saved until start and due dates are selected.
A new Event is saved under these circumstances because the current time is automatically entered if the user does not enter a date and time. But with a new Task, the user will lose all the details already entered when no warning is given.
Comment 1•14 years ago
|
||
Both start and due date are optional for tasks. You don't need to specify them. Your task will save successfully without them and is not lost. Suggesting to resolve as wontfix.
Comment 2•14 years ago
|
||
Yes I vote for WONTFIX too. I usually never set them on a task.
Updated•14 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
Thanks to you both.
In digging deeper I discovered that such a task is indeed saved in the task pane. That was not obvious to me.
However, I expect you will have users like myself who assume that new tasks will default to the current date and time just as new events do when no date information is entered. This is a potential source of confusion and frustration as it was for me.
I suggest a warning dialogue that requires the user to confirm that the omission of dates on a new task is deliberate and informs the users that the task will not appear in the calendar.
Thanks.
You need to log in
before you can comment on or make changes to this bug.
Description
•