Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
The left task requires broader configuration semantics, metric discovery, label filtering, backward compatibility, and comprehensive validation. The right task is a localized data-flow correction with focused regression coverage.
}
https://github.com/berriai/litellm/issues/30532 4:1 https://github.com/berriai/litellm/issues/29266

Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
The right-side issue is harder because it likely spans request normalization, persisted log schema compatibility, and Logs View rendering, with regression risk across multiple client formats. The left-side issue is more contained to MCP outcome classification and logging metadata.
}
https://github.com/berriai/litellm/issues/22195 3:2 https://github.com/berriai/litellm/issues/28927

Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{Custom routing requires a configurable proxy extension point, request lifecycle integration, compatibility guarantees, and broad testing; the embedding fix is comparatively localized to provider model recognition and translation coverage.}
https://github.com/berriai/litellm/issues/25297 5:1 https://github.com/berriai/litellm/issues/29786

Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
Traffic mirroring spans proxy request orchestration, asynchronous execution, provider-specific routing, failure handling, and logging/observability, creating broader integration and regression risk. The budget-window defect is more localized to update semantics, validation, persistence, and UI/API synchronization.
}
https://github.com/berriai/litellm/issues/31888 3:1 https://github.com/berriai/litellm/issues/28021

Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
The right issue is substantially harder because it is an intermittent, long-running UI failure with unclear reproduction and potentially spans frontend assets, deployment/runtime behavior, caching, and observability. The left issue is a localized fallback-semantics defect with a narrowly scoped code change and targeted regression tests.
}
https://github.com/berriai/litellm/issues/23993 5:1 https://github.com/berriai/litellm/issues/32425

Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
The right issue is harder because it requires tracing an asynchronous lifecycle across API handling, persistence, polling, provider-specific completion states, cost accounting, retries, and regression coverage. The left issue is a localized performance refactor with a comparatively narrow implementation and validation surface.
}
https://github.com/berriai/litellm/issues/35131 4:1 https://github.com/berriai/litellm/issues/31861

Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
The right issue is harder because it crosses authentication, token acquisition, health-check execution, error handling, and security-sensitive integration tests, while the left issue is comparatively localized response-field normalization and provider mapping.
}
https://github.com/berriai/litellm/issues/24709 3:1 https://github.com/berriai/litellm/issues/28461

Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
Issue 30825 requires changes to callback metadata modeling and execution paths, with compatibility considerations and broader regression testing. Issue 26668 is a narrowly scoped configuration correction.
}
https://github.com/berriai/litellm/issues/30825 10:1 https://github.com/berriai/litellm/issues/26668

Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
The left issue spans request-routing and callback lifecycle behavior across multiple API paths, requiring cross-cutting code changes and regression coverage. The right issue is more narrowly contained to database migration configuration and Prisma runtime compatibility, despite possible deployment-specific investigation.
}
https://github.com/berriai/litellm/issues/27518 3:2 https://github.com/berriai/litellm/issues/29614

Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
The right issue is harder because it spans several proxy endpoints, request-model propagation, provider selection, and identifier transformation, requiring coordinated routing and regression testing across integrations. The left issue is comparatively localized to configuration flow and runtime placeholder handling.
}
https://github.com/berriai/litellm/issues/35430 4:1 https://github.com/berriai/litellm/issues/30008