GNOME Bugzilla – Bug 263581
Evolution is not warning of conflict of appointments
Last modified: 2021-05-19 11:45:13 UTC
Please fill in this template when reporting a bug, unless you know what you are doing. Description of Problem: If i create an appointment in the time slot where already appointment is present evolution is not giving any warning before saving appointment Steps to reproduce the problem: 1. 2. 3. Actual Results: Evolution is not warning any conflict of appointments Expected Results: Evolution should warn How often does this happen? every time Additional Information: The build im using is evolution1.5-1.5.93.0.200408200541-0.snap.ximian.9.1 evolution-data-server-0.0.98.0.200408200541-0.snap.ximian.9.1
Not a regression, but something we should do.
We do this for meeting requests in the mailer now. I don't think we want to do this in the UI though.
Bumping to 2.3. We are past UI freeze for 2.2 and this needs more thought than we have time for to deal with it now.
I will work on this
Apologies for any spam... cc'ing usability-maint on all Evolution usability bugs. Filter on EVO-USABILITY-SPAM to ignore.
futuring.
Request please this be marked 2.7/2.8? Our GroupWise users reminded me today that even GroupWise 4.1 did this. This enhancement would allow you to accept without having to check the calendar each time. Currently, Evolution will gladly create conflicts :)
Currently evolution displays warnings when a meeting conflicts from the mailer for groupwise appointments.
A patch was indeed put in this for this a while back. I think this one could be closed. Evolution allows you to select sources to check for conflicts.
Please note that the original report is about the general case, creating an appointment. Neither accepting meeting requests only, nor GroupWise specific only.
Bumping version to a stable release.
*** Bug 271763 has been marked as a duplicate of this bug. ***
*** Bug 738799 has been marked as a duplicate of this bug. ***
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines and create a new enhancement request ticket at https://gitlab.gnome.org/GNOME/evolution/-/issues/ Thank you for your understanding and your help.