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

Class of Service Ordering, Naming two Classes of Service same name loses one

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 14
    • Fix Version/s: 13
    • Labels:
      None
    • ToDo:
    • Asterisk Version:
      13.22
    • Distro Version:
      Sangoma 7.5
    • Distro:
      FreePBX Distro

      Description

      My Classes of Service got all out of order somehow, making them difficult to work with, so I wanted to get them back into alphabetical order.  I tried dragging, but that didn't work.  So I started redoing them.  In doing so, I gave one the exact same name as an existing Class of Service (because I was relocating it to the new position), and it disappeared on me.  In the database, I found it in kvstore_Cos with an id of 'lookup-fc'.  I gave it a new id of a unique name and it appeared in the web interface again.

      Two issues:

      1. Don't allow people to rename a Class of Service with the same name as an existing Class of Service.
      2. Please sort the Classes of Service alphabetically, both on the Class of Service page and the Extensions -> Other page, as the current sorting (last updated appears on bottom) is a mess to work with.  Sorting alphabetically is happening in FreePBX 13 but not in 14.  That will make finding them much easier.

      Thanks,

      Dave

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                mmishra Mohit Mishra
                Reporter:
                david.sovereen@mercury.net David Sovereen
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

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