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

Allow one-time config options to be selected regardless of term and period.

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 4.0.0
    • Fix Version/s: Short Term
    • Component/s: None
    • Labels:
      None

      Description

      When selecting a Package to purchase, only the config options that match the same term and period are available. This is because the config options are considered part of the same service, and they should renew on the same schedule. (Config options are only billed when the service is renewing)

      However, one-time config options are different in that they never renew. Therefor, we should probably make any one-time config options available regardless of the term and period. In other words, if a one-time config option exists for the Package, show it regardless of the specified term and period.

      Any downside to this?

      See:
      1. https://www.blesta.com/forums/index.php?/topic/9987-make-monthlyyearly-package-support-configurable-options-with-onetime-term/
      2. https://requests.blesta.com/topic/make-mounthlyyearly-package-support-addons-onetime

        Activity

        Hide
        admin Paul Phillips added a comment -

        Since this would cause one-time options to appear for services that are not one-time, this should probably be an option. Maybe when creating/editing a config option, below "Client can Add" and "Client can Edit", add an option:

        [x] Allow one-time options for all package terms

        Show
        admin Paul Phillips added a comment - Since this would cause one-time options to appear for services that are not one-time, this should probably be an option. Maybe when creating/editing a config option, below "Client can Add" and "Client can Edit", add an option: [x] Allow one-time options for all package terms
        Hide
        jonathan Jonathan Reissmueller added a comment -

        The primary downside I see is that config options are likely invoiced with their parent service regardless of their payment period (though I could be wrong). In that case we'd have to make explicit exceptions to renewal logic preventing from being billed.

        Show
        jonathan Jonathan Reissmueller added a comment - The primary downside I see is that config options are likely invoiced with their parent service regardless of their payment period (though I could be wrong). In that case we'd have to make explicit exceptions to renewal logic preventing from being billed.

          People

          • Assignee:
            Unassigned
            Reporter:
            admin Paul Phillips
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: