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

{
Cross-layer time semantics require coordinated database, backend query, UI, migration/backward-compatibility, and regression-test work, with substantial risk around existing timestamp data. The other task is more narrowly scoped to provider/model registration and translation coverage with focused tests.
}
https://github.com/berriai/litellm/issues/25234 3:1 https://github.com/berriai/litellm/issues/32628

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

{
34619 requires broader provider architecture, external API discovery, model mapping, compatibility handling, and substantial testing; 26765 is a narrowly scoped pricing-data update with limited implementation risk.
}
https://github.com/berriai/litellm/issues/34619 8:1 https://github.com/berriai/litellm/issues/26765

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

{
29755 requires provider-specific error classification, retry policy decisions, and validation across request flows, creating broader behavioral and testing scope; 31682 currently lacks actionable detail and is primarily an investigation/triage task.
}
https://github.com/berriai/litellm/issues/29755 3:1 https://github.com/berriai/litellm/issues/31682

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

{
The right issue has greater implementation risk because it changes security-sensitive request-gating semantics, requires configuration propagation across proxy and guardrail execution paths, and needs careful backward-compatibility and failure-mode testing. The left issue is narrower, mainly involving router fallback selection, token-limit checks, and targeted retry-path tests.
}
https://github.com/berriai/litellm/issues/19779 5:3 https://github.com/berriai/litellm/issues/31557

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

{
Distributed cleanup failure requires diagnosing persistence, scheduling, locking, and error-handling interactions across deployments, plus regression coverage; the other is a narrowly scoped metadata update.
}
https://github.com/berriai/litellm/issues/16582 8:1 https://github.com/berriai/litellm/issues/34817

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

{
The left issue is harder because it is an underspecified provider/model-compatibility problem requiring investigation of API support, model metadata, request translation, and likely broader integration testing. The right issue is narrowly localized to a known transformation mapping with a comparatively contained code and regression-test change.
}
https://github.com/berriai/litellm/issues/32211 4:1 https://github.com/berriai/litellm/issues/27490

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

{
34522 requires cross-provider protocol compatibility analysis, regression tracing, and careful end-to-end tool-call validation; 33329 is a localized routing-selection correction with comparatively narrow tests.
}
https://github.com/berriai/litellm/issues/34522 4:1 https://github.com/berriai/litellm/issues/33329

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

{
A one-field response-schema correction is narrowly scoped and low risk. The other requires tracing proxy routing, background execution, configuration handling, observability, and provider-specific behavior, making investigation and regression testing substantially broader.
}
https://github.com/berriai/litellm/issues/31888 6:1 https://github.com/berriai/litellm/issues/28977

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

{
Issue #34619 is harder because it requires broader provider architecture changes, runtime discovery or extensible model routing, compatibility handling, and substantial validation across many model variants. Issue #20495 is a localized field-inheritance fix with comparatively limited testing and regression risk.
}
https://github.com/berriai/litellm/issues/34619 6:1 https://github.com/berriai/litellm/issues/20495

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

{
The left issue requires tracing identity across asynchronous batch creation and completion, extending persisted state, preserving attribution through callbacks, handling database/schema compatibility, and adding end-to-end coverage. The right issue is comparatively localized to metadata sanitization in a small number of logging paths with focused security regression tests.
}
https://github.com/berriai/litellm/issues/33316 4:1 https://github.com/berriai/litellm/issues/34710