Vishnu Narayanan 20dc4f169c fix: Do not enforce max_limits if inbox_auto_assignment is disabled (#11849) ...

# Pull Request Template

## Description

The `auto_assignment` max_limits were being enforced even if the inbox
level `auto_assign` feature was disabled. This was because the
enterprise method was not verifying the feature status before returning
the available agents.

## Type of change

Please delete options that are not relevant.

- [x] Bug fix (non-breaking change which fixes an issue)


## How Has This Been Tested?
- Tested locally
- Added Specs

## Checklist:

- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my code
- [x] I have commented on my code, particularly in hard-to-understand
areas
- [x] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [x] I have added tests that prove my fix is effective or that my
feature works
- [x] New and existing unit tests pass locally with my changes
- [x] Any dependent changes have been merged and published in downstream
modules

2025-07-01 15:10:39 -07:00

..

app

fix: Do not enforce max_limits if inbox_auto_assignment is disabled (#11849)

2025-07-01 15:10:39 -07:00

config

feat(ee): Add Captain features (#10665)

2025-01-14 16:15:47 -08:00

lib

feat: add prompt suggestions and June events (#10726)

2025-01-21 22:52:42 +05:30

LICENSE

chore: update EE LICENCE year (#11344)

2025-04-21 15:29:55 +05:30