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

{
The right issue is harder because it spans user data modeling, configuration compatibility, authorization-time enforcement, atomic budget accounting, expiration handling, and background reset behavior across shared infrastructure. The left issue is narrower, mainly involving request translation and provider-specific multipart/image handling.
}
https://github.com/berriai/litellm/issues/28235 3:2 https://github.com/berriai/litellm/issues/32456

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

{
The right issue is harder because it requires coordinated changes across data models, configuration handling, authentication-time enforcement, distributed spend counters, reservation logic, and scheduled resets, with substantial compatibility and migration risk. The left issue is primarily validation and automation of an already-defined multi-provider stack, with comparatively bounded implementation risk.
}
https://github.com/berriai/litellm/issues/28235 4:1 https://github.com/berriai/litellm/issues/26535

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

{
28168 spans many resource types, persistence layers, schemas, serialization rules, dependency ordering, and deployment/security concerns, creating substantially broader integration and compatibility risk. 28235 is a focused extension of existing budget-window mechanisms across user storage and enforcement paths.
}
https://github.com/berriai/litellm/issues/28168 4:1 https://github.com/berriai/litellm/issues/28235

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

{
Model-group composition is harder because it changes core deployment resolution and routing semantics, requiring recursive expansion, compatibility handling, and careful interaction with load balancing and rate limits. The budget-window change is substantial but can largely extend existing persistence, reservation, and reset mechanisms to another scope.
}
https://github.com/berriai/litellm/issues/28125 3:2 https://github.com/berriai/litellm/issues/28235

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

{
27883 has broader cross-tool integration scope, requiring new proxy configuration surfaces, policy translation, persistence/distribution semantics, and compatibility with two independently evolving client ecosystems. 28235 is a more contained extension of existing budget, counter, reset, and authentication paths, with clearer reuse patterns and validation boundaries.
}
https://github.com/berriai/litellm/issues/27883 3:1 https://github.com/berriai/litellm/issues/28235

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

{
The right issue is harder because it requires coordinated changes across persistence, authentication, distributed spend accounting, reset scheduling, concurrency handling, and backward compatibility. The left issue is comparatively contained within request-transformation adapters and their associated regression tests.
}
https://github.com/berriai/litellm/issues/28235 4:1 https://github.com/berriai/litellm/issues/23841

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

{
The left issue spans multiple request-conversion paths and compatibility-sensitive translation behavior, requiring coordinated code changes and broad regression testing. The right issue is a more bounded configuration-visibility change across backend and dashboard layers, with masking and precedence considerations but less protocol-surface risk.
}
https://github.com/berriai/litellm/issues/23841 3:2 https://github.com/berriai/litellm/issues/30641

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

{
The right issue is harder because it requires reliable distributed-state initialization, failure handling, readiness behavior, and automatic recovery across worker lifecycles. The left issue is broader than a single budget field but can largely extend established persistence, accounting, enforcement, and reset mechanisms.
}
https://github.com/berriai/litellm/issues/26237 5:3 https://github.com/berriai/litellm/issues/28235

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

{
The right issue is harder because it requires a security-sensitive, cross-provider change to shared credential resolution, with broad compatibility, regression, and validation risk. The left issue appears more localized to a provider-specific image-edit request path and API plumbing.
}
https://github.com/berriai/litellm/issues/31467 4:1 https://github.com/berriai/litellm/issues/32456

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

{
The export capability spans many persisted resource types, serialization and re-application semantics, secret handling, compatibility, and likely CLI/API plus extensive integration testing. The credential-routing fix is security-critical and cross-provider, but is more narrowly bounded to credential resolution, validation, and regression coverage.
}
https://github.com/berriai/litellm/issues/28168 3:1 https://github.com/berriai/litellm/issues/31467