Bug 194085
Summary: | New appointments are classified as "Private" even when "Public" was selected | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Per Nystrom <centaur> |
Component: | evolution | Assignee: | Matthew Barnes <mbarnes> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | evolution-2.8.2.1-2.fc6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-01-02 17:37:03 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Per Nystrom
2006-06-05 17:46:41 UTC
This also happens in local Evolution calendars, though that's not as much of a concern to me since local calendars are not shared to others. Changed component from evolution-connector to evolution. This appears to affect local calendars as well as Exchange calendars. This bug is still present after updating to evolution-2.6.2-1.fc5.5. Apologies for taking so long to reply. Two questions: 1) Is this bug still present in Fedora Core 6 or later? 2) I have to admit that I wasn't even aware of the classification option until reading your bug report (it's a well hidden option). Can you clarify for me what you mean when you say an appointment appears on the calendar as public or private? I tried setting up both a public and private appointment, but they look identical to me in all of the calendar views. What am I missing? 1. It seems to have been fixed sometime during FC5's cycle. It's definitely not present in FC6. 2. The difference is how the appointment looks to others who have permissions on your calendar on the Exchange server. Thanks for responding, and for enlightening me. Closing per comment #4. Feel free to re-open this if you encounter the problem again in Fedora Core 6 or later. |