-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Analytics
-
None
-
1
Issue Summary
Currently, when a Confluence page is moved from one space to another, the historical analytics data remains associated with the original space. While this is intentional to preserve historical performance records, it creates confusion in the UI.
Steps to Reproduce
- Create Initial Content: Create a new page in Space A.
- Generate Initial Data: View the page several times (e.g., 5 views) while it is located in Space A.
- Verify Space A Analytics: Navigate to Space Settings > Analytics > Content in Space A.
- Confirm the page appears in the list with the correct number of views (5).
- Move the Page: Move the page from Space A to Space B.
- Generate New Data: View the page several times (e.g., 3 views) while it is now located in Space B.
- Verify Space B Analytics: Navigate to Space Settings > Analytics > Content in Space B.
- Confirm the page appears in the list showing only the views received since the move (3).
- Verify Space A Analytics (Historical Entry): Return to the Analytics > Content tab for Space A.Observe that the page is still listed here, showing only the views it received while it lived in Space A (5).
- Check Page Analytics Aggregation: In Space A's analytics list, click the link for the moved page.
- Observed Result: The Page Analytics view opens. Although you accessed it from Space A's report, it displays the total aggregate views from both Space A and Space B (8 views).
- Consistency Check: Repeat this by clicking the link from Space B's analytics list. It also shows the same total aggregate views (8 views).
Expected Results
The UI should clearly indicate that the page has been moved from the space to avoid the appearance of "cross-space" data contamination.
Actual Results
The page remains in the original space's analytics list without any "Moved" or "Historical" indicator. Clicking it shows total aggregate views from all spaces it has inhabited, which causes confusion regarding which data belongs to which space.
Workaround
Required, if there is no workaround please state:
Currently there is no known workaround for this behavior. A workaround will be added here when available
Suggested Improvements:
- Visual Indicators: Add a label or "moved" icon next to pages in the Space Analytics Content tab that no longer reside in that space.
- Contextual Messaging: Include a tooltip or banner explaining that the analytics shown represent the period when the page was part of that specific space.
- Improved Redirection/Filtering:
-
- Option A: Allow the Page Analytics view to be filtered by space so users can see performance specifically for the time it spent in the original space.
-
- Option B: Ensure the link clearly redirects to the current space but provides a "Historical Context" view.