Skip to content

Remove workspace-specific analysis feature in favor of ResourceAnalysis #234

@halsk

Description

@halsk

Overview

Remove the legacy Slack workspace-specific analysis feature and consolidate all analysis functionality to use the ResourceAnalysis system.

Background

Currently, there are two parallel systems for channel analysis:

  1. Legacy system using SlackAnalysis and SlackChannelAnalysis tables
  2. New system using ResourceAnalysis for integration-based analysis

To simplify the codebase and user experience, we should remove the legacy system entirely.

Tasks

Frontend Changes

  • Remove /frontend/src/pages/slack/ChannelAnalysisPage.tsx
  • Remove /frontend/src/pages/slack/ChannelAnalysisHistoryPage.tsx
  • Remove analysis-related routes from App.tsx (paths containing /dashboard/analytics/slack/channels/:workspaceId/:channelId/analyze or /history)
  • Remove analysis buttons/links from WorkspaceList.tsx
  • Remove analysis tabs/sections from ChannelList.tsx
  • Remove any sidebar navigation elements related to workspace analysis
  • Add redirects or helpful messages for users looking for analysis features

Backend Changes

  • Remove table definitions for SlackAnalysis, SlackChannelAnalysis, SlackContribution, and analysis_channels
  • Remove API endpoints for workspace analysis:
    • /api/v1/slack/workspaces/{workspaceId}/channels/{channelId}/analyze
    • /api/v1/slack/workspaces/{workspaceId}/channels/{channelId}/analyses
    • /api/v1/slack/workspaces/{workspaceId}/channels/{channelId}/analyses/{analysisId}
  • Remove associated service classes specific to these endpoints
  • Update API documentation to remove references to these endpoints

Testing

  • Verify all analysis features work properly through the ResourceAnalysis system
  • Ensure no UI elements reference the removed features
  • Confirm no broken links or navigation paths

Notes

  • No data migration needed as this is not a production environment
  • All analysis functionality should be accessible through the integration paths
  • This change will simplify the codebase and reduce maintenance burden

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions