Privacy state default as preference

NEW
Unassigned

Status

--
enhancement
15 years ago
4 years ago

People

(Reporter: k_b0000, Unassigned)

Tracking

(Blocks: 2 bugs)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030812
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030812

wish:new event should remember last private selection.

bug: private event should not upload to remote calendar.
or did i mistake the meaning of private?
also it should not be removed when refreshing remote calendars (bug 215972)

Reproducible: Always

Steps to Reproduce:
(Reporter)

Updated

15 years ago
Summary: new event should remember lsat private selection and private should not upload to remote calendar → new event should remember last private selection and private should not upload to remote calendar
I think you're right on with that wish. 
At least we could have an option to tweak the default behaviour of the private
box (or did I miss that option?)

I would like to split this bug in two, the bug part is not really related to the
wishpart.
The bugpart is two bugs when you closely examins it so maybe it's three in one.

Comment 2

14 years ago
*** Bug 297798 has been marked as a duplicate of this bug. ***

Comment 3

14 years ago
Bug 297798 has been marked as a duplicate of this bug. But I'd like to request
that the preferences dialog has three possible settings for the "private" behaviour:
- Always on
- Alwarys off
- Remember last setting

The reasoning behind this, is:
1) last-setting tends to be forgotten more often, while default-behaviour is
easier to remember;
2) when the calendar is deployed by others tan the end-users, good default
settings are quite important.

I'm not quite convinced that removing private appointments from uploading the
calendar is a Good Thing. When someone uploads a private appointment, it might
quite well indicate that the specified timeslot in his/her agenda is filled (so
others cannot make appointments there).

Another thing to think about is whether this option should be on a per-calendar
base, or global. When there are a lot of calendars, a global option is
preferable, but tweaking it for each remote calendar might be usefull...

Comment 4

14 years ago
*** Bug 299692 has been marked as a duplicate of this bug. ***

Updated

13 years ago
QA Contact: gurganbl → general

Updated

13 years ago
Blocks: 312073

Updated

13 years ago
Depends on: 298102
Reassigning all automatically assigned bugs from Mostafa to nobody@m.o

Bugspam filter: TorontoMostafaMove
Assignee: mostafah → nobody

Comment 6

12 years ago
(In reply to comment #0)
> wish:new event should remember last private selection.
wish means that severify -> ENH


> bug: private event should not upload to remote calendar.
I think that it has been done by purpose - Sunbird does not split events and does not decide if event should be updated on server whether not. Remote calendar is a mirror of what is on a server and vice versa.
You could be right but this also is more enh than bug.
Severity: normal → enhancement
Regarding the "bug" portion:
This works as intended.  Marking an event as private should have no bearing on whether it is uploaded to the server or not.  If you want an event to not be uploaded to the server, add it to a local (not remote) calendar.
No longer depends on: 298102
OS: Linux → All
Hardware: PC → All
Summary: new event should remember last private selection and private should not upload to remote calendar → New event should remember last private selection
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: New event should remember last private selection → save last used privacy state in preference
Changed summary per decision on QA working session.
Summary: save last used privacy state in preference → Privacy state default as preference

Updated

11 years ago
Blocks: 400694

Comment 9

10 years ago
Here is the description I posted in the calendar newsgroup. I think this bug would partially solve it:

I have several Google calendars that I "share"[1] with my family and have integrated them into Lightning via CalDAV.

When I create a new event in a shared calendar (as defined in Google) from within Lightning, the event is created as a "private" event by default by Lightning, even though I have made no selection under "Options / Privacy" and even though Lightning showed no check-mark on any of the selections. Events created like this cannot be seen by those whom I have explicitly shared the calendar with.

Is there a way to set the default privacy setting for new Events in Lighning? I cannot (and don't want to have to) remember to explicitly set the Privacy to "Public Event" every time I create a new event in Lightning.

Is Lightning sending out an undefined privacy level, and is Google setting it to Private? Or is Lightning making all events "Private" by default (even though there is no visual indicator) and Google is just taking what Lightning is sending out?

What's the point, for a shared calendar, of setting the default to "private"? I understand that default-to-privacy is an argument. However, users can (and will) much easier create separate private and shared calendars for this purpose. And since the vast majority of users will use a calendar service (like Google), and that these services allow a much better, easier, and finer grained control of who else can see what calendars can be seen than Lightning's simple private/public setting, it would benefit most users if either:

- the default were set to "Public Event"

- the setting were directly in the dialog's primary UI (not buried in a 
  sub-menu) so users can see it easily and change it quickly

- there were a preference setting to select the default (Private or Public) 


[1] Google's description of "Privacy settings for individual events":

You can control the visibility of individual events on your calendar by selecting from these options:

* Default
Select this option if you want the event's privacy setting to mimic the calendar's privacy setting. If your calendar is private, for example, all of the events scheduled are private by default. The same concept applies to public calendars. The following two options allow you to control the visibility of specific events on public, private, and shared calendars.

* Private
For public or shared calendars, select this option to make sure only you and other calendar owners (those with 'Make changes to events' privileges and higher) can see the event and its details.

* Public
This option will make the event's details available to those with free/busy access to your calendar. If you're sharing your calendar's free/busy information with a specific person or with the world, this setting will enable them to view all of the details for the specific event. Selecting this option won't make the event's details available in public search indexes.

Note: When I create an event from within Google, the default privacy setting is "Default", which should "mimic the calendar's privacy setting" (i.e. share with the people I specified). So I doubt the problem is with Google.

Updated

10 years ago
Flags: wanted-calendar1.0?
I believe you can set up the default privacy value in the Google Calendar Web UI.
Flags: wanted-calendar1.0?
You need to log in before you can comment on or make changes to this bug.