-
Suggestion
-
Resolution: Fixed
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
This extends from TEAMCAL-537
Please see this feedback from a customer:
It does seem odd, and going to extremes, that first any user could change a calendar to any name in their own profile, then nobody but the create user can change the calendar name.
Consider the use case - user creates calendar and leaves the organisation. Then nobody can change the calendar name unless administrators reset the user's password and modify calendar name that way, or directly modify the 'owner' in the database. Both seem a little cumbersome. It would be useful if confluence-administrators could modify calendar names regardless of who owns them.
- incorporates
-
- Closed
- is duplicated by
-
- Closed
- is related to
-
- Closed
-
- Closed
- relates to
-
- Closed
[CONFCLOUD-51409] Allow users/groups access to edit the name of calendars (and edit calendars), not just the creator.
Wei Wei
added a comment - This is jeopardizing the usability of Team Calendar in my company a lot... It's hard to convince teams to use it after they discovered this issue. Please give some feedback. Thanks.
Wei Wei
added a comment - This is jeopardizing the usability of Team Calendar in my company a lot... It's hard to convince teams to use it after they discovered this issue. Please give some feedback. Thanks. Discovered another strange behaviour of TeamCalendars that show the inconsistency of its concepts:
Everyone that is not concluded by editing restrictions is able to modify the calendar restrictions!
According the plugin rules this should allowed to the "owner" only...
Uwe Kluge
added a comment - - edited Discovered another strange behaviour of TeamCalendars that show the inconsistency of its concepts:
Everyone that is not concluded by editing restrictions is able to modify the calendar restrictions!
According the plugin rules this should allowed to the "owner" only... Uwe Kluge
added a comment - Just recognized that the calendar owner will not shown elsewhere in the CF frontend. So the users don't know who to contact for changes and will create support requests to the CF admin to look in the database for the missing detail. This is another weak point for the TC plugin (that could be solved easily)!
Uwe Kluge
added a comment - Just recognized that the calendar owner will not shown elsewhere in the CF frontend. So the users don't know who to contact for changes and will create support requests to the CF admin to look in the database for the missing detail. This is another weak point for the TC plugin (that could be solved easily)! The ability to edit calendar properties within a group of users is a must-have. I think Atlassian's development team made a big mistake when introducing this concept: Confluence makes no difference between the author and possible other editors of content (users with same space permissions). This is a main deviation to the most enterprise applications (even in the collaboration area) and it was a hard job to introduce this "wiki" philosophy to our users when starting with CF. But now we see that this does not apply for TeamCalendars. I'm completely clueless how Atlassian could introduce such a concept since we are talking of shared not personal calendars here. A solution for this issue is urgently required since delegation of content administration is a basic enterprise requirement!
In addition, it would be nice if the TC concepts are described elsewhere in your documentation (did not found any statement) so users don't have to contact the support for this...
Uwe Kluge
added a comment - - edited The ability to edit calendar properties within a group of users is a must-have. I think Atlassian's development team made a big mistake when introducing this concept: Confluence makes no difference between the author and possible other editors of content (users with same space permissions). This is a main deviation to the most enterprise applications (even in the collaboration area) and it was a hard job to introduce this "wiki" philosophy to our users when starting with CF. But now we see that this does not apply for TeamCalendars. I'm completely clueless how Atlassian could introduce such a concept since we are talking of shared not personal calendars here. A solution for this issue is urgently required since delegation of content administration is a basic enterprise requirement!
In addition, it would be nice if the TC concepts are described elsewhere in your documentation (did not found any statement) so users don't have to contact the support for this...
I too am in need of being able to switch ownership of a calendar. For example I created a calendar for a leadership team. However the administrator of those meetings needs to edit the calendar and clicks on calendars at the top and doesn't see them in her list because she didn't create it. I came back to see if I could make her the admin since I am just the designer and it appears I can't do this. Hence I searched to see if this feature exists. i think its a must HAVE. Perhaps to change it to space ownership? I hope someone assigns this ASAP since it appears this has been lingering for a few years now.