-
Suggestion
-
Resolution: Fixed
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
Since Team Calendars 1.0, Calendars have lived outside spaces. What this has meant that they have a different permission and notification model to spaces.
We've learnt over the last few years that for most calendars, they really belong to a space.
We should consider changing Team Calendars so that they live in spaces. Some things to think about:
- How do we migrate existing calendars?
- You can link a calendar to a space today - we could use this
- What if the calendar has different permissions to space permissions?
- What is the experience for creating a new calendar?
- Should Calendars should be part of space export / import
It could look something like this:
http://cl.ly/image/3F3m2g0B0Z0x
- duplicates
-
CONFSERVER-48554 Add Confluence team calender programmatically
-
- Closed
-
- incorporates
-
CONFSERVER-48855 Space export doesn't bring Team calendars events.
-
- Closed
-
-
CONFSERVER-49077 Team Calendar Does not respect the Space Permission and Page restriction
- Closed
-
CONFSERVER-51223 Ability to force subscribe users to calendars
- Gathering Interest
- is related to
-
CONFSERVER-51174 Ability to restrict which groups and/or users have access to Team Calendars
- Gathering Interest
- relates to
-
CONFCLOUD-49079 Team Calendars should live in Spaces
- Closed
- Wiki Page
-
Wiki Page Loading...
[CONFSERVER-49079] Team Calendars should live in Spaces
Workflow | Original: JAC Suggestion Workflow 4 [ 3564973 ] | New: JAC Suggestion Workflow 3 [ 4330322 ] |
Workflow | Original: JAC Suggestion Workflow 2 [ 3172451 ] | New: JAC Suggestion Workflow 4 [ 3564973 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Suggestion Workflow [ 3034384 ] | New: JAC Suggestion Workflow 2 [ 3172451 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2530481 ] | New: JAC Suggestion Workflow [ 3034384 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 2285639 ] | New: Confluence Workflow - Public Facing v4 [ 2530481 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 - TEMP [ 2179681 ] | New: Confluence Workflow - Public Facing v3 [ 2285639 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 1946172 ] | New: Confluence Workflow - Public Facing v3 - TEMP [ 2179681 ] |
Workflow | Original: Confluence Workflow - Public Facing v2 [ 1761472 ] | New: Confluence Workflow - Public Facing v3 [ 1946172 ] |
Description |
Original:
Since Team Calendars 1.0, Calendars have lived outside spaces. What this has meant that they have a different permission and notification model to spaces.
We've learnt over the last few years that for most calendars, they really belong to a space. We should consider changing Team Calendars so that they live in spaces. Some things to think about: * How do we migrate existing calendars? ** You can link a calendar to a space today - we could use this ** What if the calendar has different permissions to space permissions? * What is the experience for creating a new calendar? * Should Calendars should be part of space export / import It could look something like this: http://cl.ly/image/3F3m2g0B0Z0x |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-49079]. {panel} Since Team Calendars 1.0, Calendars have lived outside spaces. What this has meant that they have a different permission and notification model to spaces. We've learnt over the last few years that for most calendars, they really belong to a space. We should consider changing Team Calendars so that they live in spaces. Some things to think about: * How do we migrate existing calendars? ** You can link a calendar to a space today - we could use this ** What if the calendar has different permissions to space permissions? * What is the experience for creating a new calendar? * Should Calendars should be part of space export / import It could look something like this: http://cl.ly/image/3F3m2g0B0Z0x |
Link |
New:
This issue relates to |