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

Plugin to change service package across package groups

    Details

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

      Description

      The current requirement that upgrades/downgrades only be performed within a given package group is there to ensure that addons and configurable options work correctly when migrating.

      However, someone mentioned the use case of moving a VPS from HDD to SSD, which were in separate package groups. They use the Universal Module, and have the addons/configurable options configured exactly the same, so it would otherwise be safe to move.

      This plugin would simply grant the ability to move a service from one package to any other package that uses the same module. Since we can't ensure compatibility (even among packages that use the same module, since they could use different module rows, etc.), a plugin is a requirement, with the disclaimer of "at your own risk".

      The plugin would need to have its own permissions, would appear under Account Actions in the client profile. It will list all services (including addons) and provide a link to change the pricing, which will take the admin to another page that details the service and gives drop-down options to change the module row and pricing:

      • The service (link back to the client profile page, and manage service page)
      • The service's current package name
      • A select menu of all module rows that use the same module (default to current module row)
      • A select menu of all packages that use the selected module row
        • After the user selects a package to migrate to, list all term/pricing options available for the package. If possible, select a term that matches the services current terms by default.

      Once the user clicks save, the plugin WOULD ONLY update the services.pricing_id and services.module_row_id.

        Activity

        cody Cody Phillips (Inactive) created issue -
        cody Cody Phillips (Inactive) made changes -
        Field Original Value New Value
        Security Private [ 10000 ]
        cody Cody Phillips (Inactive) made changes -
        Story Points 5
        cody Cody Phillips (Inactive) made changes -
        Sprint 3.6.0 Sprint 1 [ 15 ]
        cody Cody Phillips (Inactive) made changes -
        Rank Ranked higher
        cody Cody Phillips (Inactive) made changes -
        Assignee Cody Phillips [ cody ] Tyson Phillips [ tyson ]
        cody Cody Phillips (Inactive) made changes -
        Fix Version/s 3.6.0 [ 10600 ]
        tyson Tyson Phillips (Inactive) made changes -
        Description The current requirement that upgrades/downgrades only be performed within a given package group is there to ensure that addons and configurable options work correctly when migrating.

        However, someone mentioned the use case of moving a VPS from HDD to SSD, which were in separate package groups. They use the Universal Module, and have the addons/configurable options configured exactly the same, so it would otherwise be safe to move.

        This plugin would simply grant the ability to move a service from one package to any other package *that uses the same module*. Since we can't ensure compatibility (even among packages that use the same module, since they could use different module rows, etc.), a plugin is a requirement, with the disclaimer of "at your own risk".

        The plugin would need to have its own permissions, would appear under *Tools*, and ask for the service to move (service ID or service number). It would then list:

        - The service (link back to the client profile page, and manage service page)
        - The service's current package name
        - A select menu of all module rows that use the same module (default to current module row)
        - A select menu of all packages that use the selected module row
        -- After the user selects a package to migrate to, list all term/pricing options available for the package. If possible, select a term that matches the services current terms by default.

        Once the user clicks save, the plugin *WOULD ONLY* update the *services.pricing_id* and *services.module_row_id*.
        The current requirement that upgrades/downgrades only be performed within a given package group is there to ensure that addons and configurable options work correctly when migrating.

        However, someone mentioned the use case of moving a VPS from HDD to SSD, which were in separate package groups. They use the Universal Module, and have the addons/configurable options configured exactly the same, so it would otherwise be safe to move.

        This plugin would simply grant the ability to move a service from one package to any other package *that uses the same module*. Since we can't ensure compatibility (even among packages that use the same module, since they could use different module rows, etc.), a plugin is a requirement, with the disclaimer of "at your own risk".

        The plugin would need to have its own permissions, would appear under Account Actions in the client profile. It will list all services (including addons) and provide a link to change the pricing, which will take the admin to another page that details the service and gives drop-down options to change the module row and pricing:

        - The service (link back to the client profile page, and manage service page)
        - The service's current package name
        - A select menu of all module rows that use the same module (default to current module row)
        - A select menu of all packages that use the selected module row
        -- After the user selects a package to migrate to, list all term/pricing options available for the package. If possible, select a term that matches the services current terms by default.

        Once the user clicks save, the plugin *WOULD ONLY* update the *services.pricing_id* and *services.module_row_id*.
        tyson Tyson Phillips (Inactive) made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        tyson Tyson Phillips (Inactive) made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        tyson Tyson Phillips (Inactive) made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

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

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              28/Sep/15

              Agile