Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-22294

New Queue API destroys queue if sent with no static members

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 15, 16
    • Fix Version/s: 15, 16
    • Component/s: Queues
    • Labels:
      None
    • Bug Tracker:
      Customer Issue
    • ToDo:
    • Asterisk Version:
      16.13.0
    • Distro Version:
      15
    • Distro:
      FreePBX Distro
    • Module Fix Version:

      Description

      From FreePBX Pull request 22110, by xavifrhttps://git.freepbx.org/projects/FREEPBX/repos/queues/pull-requests/48/diff

      in the edge track for the queues module
       15.0.3.11 there is a new set of API calls for the queues module.

      if you try to remove Static Members by sending members=.  the API call will shred your queue (and reset it to the default queue state - no name, no customized settings, nothing.)

      if you remove dynamic members in the same way (`dynmember=`, it successfully clears the dynamic member list.

      Specific tests that can trigger this
      PUT to `[http://\|http:]SERVER/admin/api/api/rest/queues/members/999`
      body: x-www-form-urlencoded
      members: 123
      dynmanber: 124
      ^^ will set both types of agent

      members:
      dynmember: 124
      ^^ will break your queue

      member: 123
      dynmember:
      ^ will clear dynamic members

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  sholinaty sholinaty
                  Reporter:
                  sholinaty sholinaty
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    NextupJiraPlusStatus

                    Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.