-
Bug
-
Resolution: Low Engagement
-
Medium
-
None
-
5.3.10
-
Confluence 5.9.5
-
Severity 2 - Major
-
We are planning to upgrade Confluence to latest version 5.9.5. Mandate is we need to have Team Calendar 5.3.9+ to be compatible with this Wiki version.
With this annoying feature TEAMCAL-3147, one has to have Wiki Space associated to given Calendar. (Can anyone tell me, why there should be relation, why can't we make it optional)
And the trouble is if we want to associate the Wiki Space with calendar, it just doesn't accept the Wiki Space name or Wiki Key. Wiki throws error saying "No Space Found". Quick investigation reveals that internally it uses rest api call like this
https://<wiki-instance>/rest/prototype/1/search/name.json?max-results=5&pageSize=5&type=spacedesc%2Cpersonalspacedesc&query=queryterm
As you can see, API calls searches in Space Description rather than Space Key or Space Name, which in my opinion is not set by most teams (at least that is the case in our company)
I've also confirmed that by updating space description, it does work. But the question why it's not very obvious in error description. or why not reterieve all three parameters (spacename, spacedesc and space name) and then make decision.
Hope this helps.
Thank you,
Raju
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
[CONFSERVER-48555] Unable to enter required "Wiki Space" for Calendar
| QA Demo Status | New: Not Needed [ 14332 ] | |
| QA Kickoff Status | New: Not Needed [ 14236 ] | |
| Resolution | New: Low Engagement [ 10300 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Labels | Original: affects-server | New: affects-server cleanup-seos-fy25 |
| Remote Link | New: This issue links to "Page (Extranet)" [ 494517 ] |
| Workflow | Original: JAC Bug Workflow v3 [ 2900633 ] | New: CONFSERVER Bug Workflow v4 [ 2995369 ] |
| Workflow | Original: JAC Bug Workflow v2 [ 2795961 ] | New: JAC Bug Workflow v3 [ 2900633 ] |
| Workflow | Original: JAC Bug Workflow [ 2726003 ] | New: JAC Bug Workflow v2 [ 2795961 ] |
| Symptom Severity | Original: Major [ 14431 ] | New: Severity 2 - Major [ 15831 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2389959 ] | New: JAC Bug Workflow [ 2726003 ] |
| Status | Original: Open [ 1 ] | New: Gathering Impact [ 12072 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2268639 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2389959 ] |
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Confluence Data Center