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

Coupons: Add option for Configurable Option Limitation

    Details

      Description

      When creating/editing a coupon, add a section below "Term Limitations" called "Configurable Option Limitations".

      We want to be able to limit a coupon to also require the selection of a specific configurable option and value. This will allow a single config option to be selected, but we may expand this in the future to additional config option limitations. One for now.

      Add a dropdown menu of Config Option Groups, default to "None". When a Config Option Group is selected, populate a dropdown of Configurable Options assigned to that group. (The group is only for sorting, if the option we select belongs to multiple groups then it will work for all groups it is assigned, not just the one selected We may want to indicate this here.)

      When a Configurable Option is selected within the group, display the available options and allow 1 or more to be selected. This will depend on the type.

      • For radio and dropdown, show a multi-select of options.
      • For checkbox, show the value in a multi-select (it can either be selected or not)
      • For quantity, display an input field for "Minimum Quantity". At least this many must be selected.
      • For text, textarea, and password we can either use a regex or simply require something be entered (do we need a regex?)

      The coupon will only apply if it meets all the limitations, for the assigned packages, etc like it does now, but if a config option limitation is set it must also meet that limitation to apply.

      Use Case

      Consider a dedicated server with a config option for the number of CPU's. The dropdown has 4 options. 1 CPU, 2 CPU's, 3 CPU's, 4 CPU's. We want the coupon to apply only if they select 3 or 4 CPU's.

      In our configuration, we would select the group, then the config option for CPU's, and in the multi-select we would select 3 CPU's, and 4 CPU's (but not 1 and 2).

      The order plugin may need to be updated to enforce this as well.

        Activity

        admin Paul Phillips created issue -
        admin Paul Phillips made changes -
        Field Original Value New Value
        Description Add an option below "Term Limitations" called "Configurable Option Limitations".

        We want to be able to limit a coupon to also require the selection of a specific configurable option and value. This will allow a single config option to be selected, but we may expand this in the future to additional config option limitations. One for now.

        Add a dropdown menu of Config Option Groups, default to "None". When a Config Option Group is selected, populate a dropdown of Configurable Options within that group.

        When a Configurable Option is selected within the group, display the available options and allow 1 or more to be selected. This will depend on the type.

        - For radio and dropdown, show a multi-select of options.
        - For checkbox, show the value in a multi-select (it can either be selected or not)
        - For quantity, display an input field for "Minimum Quantity". At least this many must be selected.
        - For text, textarea, and password we can either use a regex or simply require something be entered (do we need a regex?)

        The coupon will only apply if it meets all the limitations, for the assigned packages, etc like it does now, but if a config option limitation is set it must also meet that limitation to apply.

        ## Use Case

        Consider a dedicated server with a config option for the number of CPU's. The dropdown has 4 options. 1 CPU, 2 CPU's, 3 CPU's, 4 CPU's. We want the coupon to apply only if they select 3 or 4 CPU's.

        In our configuration, we would select the group, then the config option for CPU's, and in the multi-select we would select 3 CPU's, and 4 CPU's (but not 1 and 2).

        The order plugin may need to be updated to enforce this as well.


        Add an option below "Term Limitations" called "Configurable Option Limitations".

        We want to be able to limit a coupon to also require the selection of a specific configurable option and value. This will allow a single config option to be selected, but we may expand this in the future to additional config option limitations. One for now.

        Add a dropdown menu of Config Option Groups, default to "None". When a Config Option Group is selected, populate a dropdown of Configurable Options within that group.

        When a Configurable Option is selected within the group, display the available options and allow 1 or more to be selected. This will depend on the type.

        - For radio and dropdown, show a multi-select of options.
        - For checkbox, show the value in a multi-select (it can either be selected or not)
        - For quantity, display an input field for "Minimum Quantity". At least this many must be selected.
        - For text, textarea, and password we can either use a regex or simply require something be entered (do we need a regex?)

        The coupon will only apply if it meets all the limitations, for the assigned packages, etc like it does now, but if a config option limitation is set it must also meet that limitation to apply.

        # Use Case

        Consider a dedicated server with a config option for the number of CPU's. The dropdown has 4 options. 1 CPU, 2 CPU's, 3 CPU's, 4 CPU's. We want the coupon to apply only if they select 3 or 4 CPU's.

        In our configuration, we would select the group, then the config option for CPU's, and in the multi-select we would select 3 CPU's, and 4 CPU's (but not 1 and 2).

        The order plugin may need to be updated to enforce this as well.


        admin Paul Phillips made changes -
        Description Add an option below "Term Limitations" called "Configurable Option Limitations".

        We want to be able to limit a coupon to also require the selection of a specific configurable option and value. This will allow a single config option to be selected, but we may expand this in the future to additional config option limitations. One for now.

        Add a dropdown menu of Config Option Groups, default to "None". When a Config Option Group is selected, populate a dropdown of Configurable Options within that group.

        When a Configurable Option is selected within the group, display the available options and allow 1 or more to be selected. This will depend on the type.

        - For radio and dropdown, show a multi-select of options.
        - For checkbox, show the value in a multi-select (it can either be selected or not)
        - For quantity, display an input field for "Minimum Quantity". At least this many must be selected.
        - For text, textarea, and password we can either use a regex or simply require something be entered (do we need a regex?)

        The coupon will only apply if it meets all the limitations, for the assigned packages, etc like it does now, but if a config option limitation is set it must also meet that limitation to apply.

        # Use Case

        Consider a dedicated server with a config option for the number of CPU's. The dropdown has 4 options. 1 CPU, 2 CPU's, 3 CPU's, 4 CPU's. We want the coupon to apply only if they select 3 or 4 CPU's.

        In our configuration, we would select the group, then the config option for CPU's, and in the multi-select we would select 3 CPU's, and 4 CPU's (but not 1 and 2).

        The order plugin may need to be updated to enforce this as well.


        Add an option below "Term Limitations" called "Configurable Option Limitations".

        We want to be able to limit a coupon to also require the selection of a specific configurable option and value. This will allow a single config option to be selected, but we may expand this in the future to additional config option limitations. One for now.

        Add a dropdown menu of Config Option Groups, default to "None". When a Config Option Group is selected, populate a dropdown of Configurable Options within that group.

        When a Configurable Option is selected within the group, display the available options and allow 1 or more to be selected. This will depend on the type.

        - For radio and dropdown, show a multi-select of options.
        - For checkbox, show the value in a multi-select (it can either be selected or not)
        - For quantity, display an input field for "Minimum Quantity". At least this many must be selected.
        - For text, textarea, and password we can either use a regex or simply require something be entered (do we need a regex?)

        The coupon will only apply if it meets all the limitations, for the assigned packages, etc like it does now, but if a config option limitation is set it must also meet that limitation to apply.

        h2. Use Case

        Consider a dedicated server with a config option for the number of CPU's. The dropdown has 4 options. 1 CPU, 2 CPU's, 3 CPU's, 4 CPU's. We want the coupon to apply only if they select 3 or 4 CPU's.

        In our configuration, we would select the group, then the config option for CPU's, and in the multi-select we would select 3 CPU's, and 4 CPU's (but not 1 and 2).

        The order plugin may need to be updated to enforce this as well.


        admin Paul Phillips made changes -
        Description Add an option below "Term Limitations" called "Configurable Option Limitations".

        We want to be able to limit a coupon to also require the selection of a specific configurable option and value. This will allow a single config option to be selected, but we may expand this in the future to additional config option limitations. One for now.

        Add a dropdown menu of Config Option Groups, default to "None". When a Config Option Group is selected, populate a dropdown of Configurable Options within that group.

        When a Configurable Option is selected within the group, display the available options and allow 1 or more to be selected. This will depend on the type.

        - For radio and dropdown, show a multi-select of options.
        - For checkbox, show the value in a multi-select (it can either be selected or not)
        - For quantity, display an input field for "Minimum Quantity". At least this many must be selected.
        - For text, textarea, and password we can either use a regex or simply require something be entered (do we need a regex?)

        The coupon will only apply if it meets all the limitations, for the assigned packages, etc like it does now, but if a config option limitation is set it must also meet that limitation to apply.

        h2. Use Case

        Consider a dedicated server with a config option for the number of CPU's. The dropdown has 4 options. 1 CPU, 2 CPU's, 3 CPU's, 4 CPU's. We want the coupon to apply only if they select 3 or 4 CPU's.

        In our configuration, we would select the group, then the config option for CPU's, and in the multi-select we would select 3 CPU's, and 4 CPU's (but not 1 and 2).

        The order plugin may need to be updated to enforce this as well.


        When creating/editing a coupon, add a section below "Term Limitations" called "Configurable Option Limitations".

        We want to be able to limit a coupon to also require the selection of a specific configurable option and value. This will allow a single config option to be selected, but we may expand this in the future to additional config option limitations. One for now.

        Add a dropdown menu of Config Option Groups, default to "None". When a Config Option Group is selected, populate a dropdown of Configurable Options within that group.

        When a Configurable Option is selected within the group, display the available options and allow 1 or more to be selected. This will depend on the type.

        - For radio and dropdown, show a multi-select of options.
        - For checkbox, show the value in a multi-select (it can either be selected or not)
        - For quantity, display an input field for "Minimum Quantity". At least this many must be selected.
        - For text, textarea, and password we can either use a regex or simply require something be entered (do we need a regex?)

        The coupon will only apply if it meets all the limitations, for the assigned packages, etc like it does now, but if a config option limitation is set it must also meet that limitation to apply.

        h2. Use Case

        Consider a dedicated server with a config option for the number of CPU's. The dropdown has 4 options. 1 CPU, 2 CPU's, 3 CPU's, 4 CPU's. We want the coupon to apply only if they select 3 or 4 CPU's.

        In our configuration, we would select the group, then the config option for CPU's, and in the multi-select we would select 3 CPU's, and 4 CPU's (but not 1 and 2).

        The order plugin may need to be updated to enforce this as well.


        admin Paul Phillips made changes -
        Description When creating/editing a coupon, add a section below "Term Limitations" called "Configurable Option Limitations".

        We want to be able to limit a coupon to also require the selection of a specific configurable option and value. This will allow a single config option to be selected, but we may expand this in the future to additional config option limitations. One for now.

        Add a dropdown menu of Config Option Groups, default to "None". When a Config Option Group is selected, populate a dropdown of Configurable Options within that group.

        When a Configurable Option is selected within the group, display the available options and allow 1 or more to be selected. This will depend on the type.

        - For radio and dropdown, show a multi-select of options.
        - For checkbox, show the value in a multi-select (it can either be selected or not)
        - For quantity, display an input field for "Minimum Quantity". At least this many must be selected.
        - For text, textarea, and password we can either use a regex or simply require something be entered (do we need a regex?)

        The coupon will only apply if it meets all the limitations, for the assigned packages, etc like it does now, but if a config option limitation is set it must also meet that limitation to apply.

        h2. Use Case

        Consider a dedicated server with a config option for the number of CPU's. The dropdown has 4 options. 1 CPU, 2 CPU's, 3 CPU's, 4 CPU's. We want the coupon to apply only if they select 3 or 4 CPU's.

        In our configuration, we would select the group, then the config option for CPU's, and in the multi-select we would select 3 CPU's, and 4 CPU's (but not 1 and 2).

        The order plugin may need to be updated to enforce this as well.


        When creating/editing a coupon, add a section below "Term Limitations" called "Configurable Option Limitations".

        We want to be able to limit a coupon to also require the selection of a specific configurable option and value. This will allow a single config option to be selected, but we may expand this in the future to additional config option limitations. One for now.

        Add a dropdown menu of Config Option Groups, default to "None". When a Config Option Group is selected, populate a dropdown of Configurable Options assigned to that group. (**The group is only for sorting, if the option we select belongs to multiple groups then it will work for all groups** We may want to indicate this)

        When a Configurable Option is selected within the group, display the available options and allow 1 or more to be selected. This will depend on the type.

        - For radio and dropdown, show a multi-select of options.
        - For checkbox, show the value in a multi-select (it can either be selected or not)
        - For quantity, display an input field for "Minimum Quantity". At least this many must be selected.
        - For text, textarea, and password we can either use a regex or simply require something be entered (do we need a regex?)

        The coupon will only apply if it meets all the limitations, for the assigned packages, etc like it does now, but if a config option limitation is set it must also meet that limitation to apply.

        h2. Use Case

        Consider a dedicated server with a config option for the number of CPU's. The dropdown has 4 options. 1 CPU, 2 CPU's, 3 CPU's, 4 CPU's. We want the coupon to apply only if they select 3 or 4 CPU's.

        In our configuration, we would select the group, then the config option for CPU's, and in the multi-select we would select 3 CPU's, and 4 CPU's (but not 1 and 2).

        The order plugin may need to be updated to enforce this as well.


        admin Paul Phillips made changes -
        Description When creating/editing a coupon, add a section below "Term Limitations" called "Configurable Option Limitations".

        We want to be able to limit a coupon to also require the selection of a specific configurable option and value. This will allow a single config option to be selected, but we may expand this in the future to additional config option limitations. One for now.

        Add a dropdown menu of Config Option Groups, default to "None". When a Config Option Group is selected, populate a dropdown of Configurable Options assigned to that group. (**The group is only for sorting, if the option we select belongs to multiple groups then it will work for all groups** We may want to indicate this)

        When a Configurable Option is selected within the group, display the available options and allow 1 or more to be selected. This will depend on the type.

        - For radio and dropdown, show a multi-select of options.
        - For checkbox, show the value in a multi-select (it can either be selected or not)
        - For quantity, display an input field for "Minimum Quantity". At least this many must be selected.
        - For text, textarea, and password we can either use a regex or simply require something be entered (do we need a regex?)

        The coupon will only apply if it meets all the limitations, for the assigned packages, etc like it does now, but if a config option limitation is set it must also meet that limitation to apply.

        h2. Use Case

        Consider a dedicated server with a config option for the number of CPU's. The dropdown has 4 options. 1 CPU, 2 CPU's, 3 CPU's, 4 CPU's. We want the coupon to apply only if they select 3 or 4 CPU's.

        In our configuration, we would select the group, then the config option for CPU's, and in the multi-select we would select 3 CPU's, and 4 CPU's (but not 1 and 2).

        The order plugin may need to be updated to enforce this as well.


        When creating/editing a coupon, add a section below "Term Limitations" called "Configurable Option Limitations".

        We want to be able to limit a coupon to also require the selection of a specific configurable option and value. This will allow a single config option to be selected, but we may expand this in the future to additional config option limitations. One for now.

        Add a dropdown menu of Config Option Groups, default to "None". When a Config Option Group is selected, populate a dropdown of Configurable Options assigned to that group. (*The group is only for sorting, if the option we select belongs to multiple groups then it will work for all groups, not just the one selected* We may want to indicate this here.)

        When a Configurable Option is selected within the group, display the available options and allow 1 or more to be selected. This will depend on the type.

        - For radio and dropdown, show a multi-select of options.
        - For checkbox, show the value in a multi-select (it can either be selected or not)
        - For quantity, display an input field for "Minimum Quantity". At least this many must be selected.
        - For text, textarea, and password we can either use a regex or simply require something be entered (do we need a regex?)

        The coupon will only apply if it meets all the limitations, for the assigned packages, etc like it does now, but if a config option limitation is set it must also meet that limitation to apply.

        h2. Use Case

        Consider a dedicated server with a config option for the number of CPU's. The dropdown has 4 options. 1 CPU, 2 CPU's, 3 CPU's, 4 CPU's. We want the coupon to apply only if they select 3 or 4 CPU's.

        In our configuration, we would select the group, then the config option for CPU's, and in the multi-select we would select 3 CPU's, and 4 CPU's (but not 1 and 2).

        The order plugin may need to be updated to enforce this as well.


        admin Paul Phillips made changes -
        Description When creating/editing a coupon, add a section below "Term Limitations" called "Configurable Option Limitations".

        We want to be able to limit a coupon to also require the selection of a specific configurable option and value. This will allow a single config option to be selected, but we may expand this in the future to additional config option limitations. One for now.

        Add a dropdown menu of Config Option Groups, default to "None". When a Config Option Group is selected, populate a dropdown of Configurable Options assigned to that group. (*The group is only for sorting, if the option we select belongs to multiple groups then it will work for all groups, not just the one selected* We may want to indicate this here.)

        When a Configurable Option is selected within the group, display the available options and allow 1 or more to be selected. This will depend on the type.

        - For radio and dropdown, show a multi-select of options.
        - For checkbox, show the value in a multi-select (it can either be selected or not)
        - For quantity, display an input field for "Minimum Quantity". At least this many must be selected.
        - For text, textarea, and password we can either use a regex or simply require something be entered (do we need a regex?)

        The coupon will only apply if it meets all the limitations, for the assigned packages, etc like it does now, but if a config option limitation is set it must also meet that limitation to apply.

        h2. Use Case

        Consider a dedicated server with a config option for the number of CPU's. The dropdown has 4 options. 1 CPU, 2 CPU's, 3 CPU's, 4 CPU's. We want the coupon to apply only if they select 3 or 4 CPU's.

        In our configuration, we would select the group, then the config option for CPU's, and in the multi-select we would select 3 CPU's, and 4 CPU's (but not 1 and 2).

        The order plugin may need to be updated to enforce this as well.


        When creating/editing a coupon, add a section below "Term Limitations" called "Configurable Option Limitations".

        We want to be able to limit a coupon to also require the selection of a specific configurable option and value. This will allow a single config option to be selected, but we may expand this in the future to additional config option limitations. One for now.

        Add a dropdown menu of Config Option Groups, default to "None". When a Config Option Group is selected, populate a dropdown of Configurable Options assigned to that group. (*The group is only for sorting, if the option we select belongs to multiple groups then it will work for all groups it is assigned, not just the one selected* We may want to indicate this here.)

        When a Configurable Option is selected within the group, display the available options and allow 1 or more to be selected. This will depend on the type.

        - For radio and dropdown, show a multi-select of options.
        - For checkbox, show the value in a multi-select (it can either be selected or not)
        - For quantity, display an input field for "Minimum Quantity". At least this many must be selected.
        - For text, textarea, and password we can either use a regex or simply require something be entered (do we need a regex?)

        The coupon will only apply if it meets all the limitations, for the assigned packages, etc like it does now, but if a config option limitation is set it must also meet that limitation to apply.

        h2. Use Case

        Consider a dedicated server with a config option for the number of CPU's. The dropdown has 4 options. 1 CPU, 2 CPU's, 3 CPU's, 4 CPU's. We want the coupon to apply only if they select 3 or 4 CPU's.

        In our configuration, we would select the group, then the config option for CPU's, and in the multi-select we would select 3 CPU's, and 4 CPU's (but not 1 and 2).

        The order plugin may need to be updated to enforce this as well.


        admin Paul Phillips made changes -
        Rank Ranked higher
        admin Paul Phillips made changes -
        Assignee Jonathan Reissmueller [ jonathan ]
        admin Paul Phillips made changes -
        Priority Major [ 3 ] Blocker [ 1 ]

          People

          • Assignee:
            jonathan Jonathan Reissmueller
            Reporter:
            admin Paul Phillips
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: