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 256066 - private appts should show in other users calendar
private appts should show in other users calendar
Status: RESOLVED WONTFIX
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
1.4.6
Other All
: Normal minor
: reschedule
Assigned To: Connector Maintainer
Ximian Connector QA
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2004-03-26 11:16 UTC by Olly Stephens
Modified: 2013-07-23 14:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Olly Stephens 2004-03-26 11:16:22 UTC
Description of Problem:

  The handling of "private" appointments in evo differs from outlook.
  I presume it's just a different interpretation of the data.

  If someone creates a "private" appt in their calendar, I see nothing
  when viewing their calendar through evo, but if I try and schedule a
  meeting with them, it shows the time as busy.

  Using outlook, I see the appt in their calendar but it's marked
  private so I cannot see the detail.

  Personally, I feel the way outlook handles it is less confusing.

Steps to reproduce the problem:

  1. get someone else to create a private meeting in their calendar 
  2. view their calendar using evo and using outlook (or owa)

Actual Results:

  Outlook and OWA show the private appointment but label it so
  Evo shows nothing

Expected Results:

  Evo shows private appointment but labels it so

How often does this happen? 

  Always

Additional Information:

  None
Comment 1 Dan Winship 2004-09-02 19:12:30 UTC
this is fixable, but it would be fairly annoying to do so
Comment 2 André Klapper 2012-09-20 14:47:58 UTC
The "evolution-exchange" package only supports Exchange 2000 and 2003 servers. Newer versions such as Exchange 2007 and 2010 are not supported by "evolution-exchange". It is required to use the package "evolution-ews" (or to some extend "evolution-mapi") for newer version fo Exchange servers.

If the problem/request described in this report still happens with a recent version of "evolution-ews" or "evolution-mapi", please add a comment to this report (and update the "product" setting accordingly if possible).

There are currently no plans to continue the development of the package "evolution-exchange", so this report will soon be closed as WONTFIX.
Thanks for your understanding and sorry that the reported problem was not solved in time in the package "evolution-exchange".
Comment 3 André Klapper 2013-07-23 14:27:49 UTC
evolution-exchange only supports the older Microsoft Exchange server versions 2000 and 2003. The last stable release of evolution-exchange was 3.4.4 which took place a year ago.

evolution-exchange is now deprecated and not under active development anymore.

It is unlikely that there will be any further active development.

Closing this report as WONTFIX as part of Bugzilla Housekeeping.

Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again.

Also feel free to reopen this ticket and change the "Product" field accordingly if the reported issue still happens with a recent version (newer than version 3.6) of one of those Exchange backends that are still supported.
Please see https://help.gnome.org/users/evolution/3.8/exchange-connectors-overview.html for more information on available backends.