• Type: Sub-task
    • Resolution: Done
    • Priority: Low
    • None
    • Affects Version/s: None
    • None
    • AMRIT Sprint 29, AMRIT Sprint 30, AMRIT Sprint 31, AMRIT Sprint 32, AMRIT Sprint 33, AMRIT Sprint 34, AMRIT Sprint 35, AMRIT Sprint 36, AMRIT Sprint 38
    • ECD
    • Dev

      As an associate, I want the Re-allocation API to follow the correct introductory allocation logic, so that when a call is re-allocated, the language preferences are preserved and accurately reflected on the Closure screen.

      Ensures that the Re-allocation API applies introductory allocation rules properly during re-allocation, especially regarding language matching.

      Acceptance Criteria:

      • The API logic uses introductory allocation parameters.
      • Preferred language is correctly retained or reassigned in re-allocation scenarios.
      • Closure screen reflects the updated and correct preferred language post re-allocation.
      • No impact on re-allocation logic for other user roles or call types.

            Assignee:
            Ravi Shanigarapu
            Reporter:
            Devika S
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 1 day, 4 hours
                1d 4h
                Remaining:
                Remaining Estimate - 1 day, 4 hours
                1d 4h
                Logged:
                Time Spent - Not Specified
                Not Specified