Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-2156

Allow the module row to be selected when adding a service

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.6.0
    • Fix Version/s: 4.6.0-b1
    • Component/s: Modules
    • Labels:
      None

      Description

      When an admin creates a service, allow the module row to be selected to provision it on. For example, with cPanel, sometimes you may want to provision the service on a specific server.

      1. When creating a service as an admin, add:
        1. A checkbox under Send order confirmation email when activated
          • Have the label read "Assign the service to a specific module row"
          • Add a tooltip that reads "The service will choose a module row based on the module configuration unless this is checked"
        2. A select option listing all of the module rows available for the module
          • Group the module rows by module group, if any
          • Default to selecting the module row based on the package configuration

      When an admin adds a cPanel service manually, it is sometimes necessary for the admin to be able to specify which server to provision the account on, rather than allowing the system to determine this automatically.

      When adding or activating a cPanel service manually as an admin, add a drop down menu so that a specific server can be selected.

      May need further discussion. See original feature request at http://www.blesta.com/forums/index.php?/topic/6293-cpanel-allow-staff-to-choose-wich-server-to-create-the-account/

        Issue Links

          Activity

            People

            • Assignee:
              tyson Tyson Phillips (Inactive)
              Reporter:
              admin Paul Phillips
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                28/May/19

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 3 hours, 53 minutes
                3h 53m

                  Agile