phpgroupware-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Phpgroupware-tracker] [bugs #3853] Incomplete "scheduling conflict" war


From: Dave Hall
Subject: [Phpgroupware-tracker] [bugs #3853] Incomplete "scheduling conflict" warning
Date: Wed, 14 Jul 2004 23:49:02 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040602 Firefox/0.8

This mail is an automated notification from the bugs tracker
 of the project: phpGroupWare.

/**************************************************************************/
[bugs #3853] Latest Modifications:

Changes by: 
                Dave Hall <address@hidden>
'Date: 
                Thu 07/15/2004 at 03:46 (Australia/Melbourne)

            What     | Removed                   | Added
---------------------------------------------------------------------------
         Assigned to | skeeter                   | skwashd







/**************************************************************************/
[bugs #3853] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=3853>
Project: phpGroupWare
Submitted by: 0
On: Mon 06/02/2003 at 17:28

Category:  calendar
Item Group:  0.9.14.003 release
Severity:  5 - Average
Priority:  5 - Normal
Resolution:  None
Assigned to:  skwashd
Status:  Open
Component Version:  BZIP2
Platform Version:  GNU/Linux - RedHat/Fedora
Reproducibility:  Every Time


Summary:  Incomplete "scheduling conflict" warning

Original Submission:  Suppose that a user tries to add an event to 20/06, 
10:00-11:00, with two (or more) participants and that one of them already has a 
"private" event scheduled to the same date/time. The user will get a scheduling 
conflict warning, but it will NOT point out whom the conflicting event belongs 
to.











For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=3853>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/







reply via email to

[Prev in Thread] Current Thread [Next in Thread]