After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 353794 - Confirmation message for tasks without summary is not correct.
Confirmation message for tasks without summary is not correct.
Status: RESOLVED DUPLICATE of bug 609052
Product: evolution
Classification: Applications
Component: Tasks
2.8.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Johnny Jacob
Evolution QA team
: 273437 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-09-01 09:12 UTC by ushveen kaur
Modified: 2012-01-29 12:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch created. (6.13 KB, patch)
2006-09-11 05:41 UTC, ushveen kaur
needs-work Details | Review

Description ushveen kaur 2006-09-01 09:12:24 UTC
Steps to reproduce:
1. Create a new task(not an assigned task).
2. Fill some fields of this task but leave the "summary" field empty.
3. Save this task.

Actual result:
The confimation popup says "Adding a meaningful summary to your task will give your recipients an idea of what your task is about.", whereas there are no recipients here.
Also the two buttons on this popup are "Cancel" and "Send"

Expected result:
The confirmation popup should ask if the task should be saved without a summary?
Also the buttons on the popup sould be "Cancel" and "Save".
Comment 1 ushveen kaur 2006-09-11 05:41:15 UTC
Created attachment 72525 [details] [review]
Patch created.
Comment 2 André Klapper 2006-09-12 09:52:27 UTC
*** Bug 273437 has been marked as a duplicate of this bug. ***
Comment 3 Johnny Jacob 2007-08-23 16:26:17 UTC
Couldn't apply on trunk. marking as needs-work. 
Comment 4 Matthew Barnes 2008-03-11 00:28:00 UTC
Bumping version to a stable release.
Comment 5 André Klapper 2012-01-29 12:07:54 UTC
This was fixed by bug 609052

*** This bug has been marked as a duplicate of bug 609052 ***