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

Add client permissions scheme to configurable options

        Details

          Description

          Configurable options should have permissions:

          [x] Client Add
          [x] Client Edit

          A client add permission means that clients will be able to add the config option, and it will appear on order forms. A client edit permission means the client can change it within the client area as part of config option upgrades - CORE-1447

            Issue Links

            blocks

            Epic - Created by JIRA Agile - do not edit or delete. Issue type for a big user story that needs to be broken down. CORE-1447 Upgrades/downgrades for configurable options

            • Major - Major loss of function.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. CORE-1478 Allow clients to update config options

            • Major - Major loss of function.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. CORE-1545 Order: Allow clients to add config options

            • Major - Major loss of function.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. CORE-1546 Allow clients to add config options

            • Major - Major loss of function.
            • Closed

              Activity

              Ascending order - Click to sort in descending order
              admin Paul Phillips created issue -
              Hide
              Permalink
              admin Paul Phillips added a comment -

              A "Maximum" value a client may order, or upgrade to in the client area has been proposed. A use case are IP addresses. Hosting providers want to allow a client to order say up to 5 IP addresses during checkout. Later, once their account is provisioned, they could upgrade their configurable options beyond this limit. The limit would also not apply to staff.

              I wonder if this would make sense as an option to quantities only, or if there is a way to provide limits on other config option field types as well. *This needs further discussion*

              Show
              admin Paul Phillips added a comment - A "Maximum" value a client may order, or upgrade to in the client area has been proposed. A use case are IP addresses. Hosting providers want to allow a client to order say up to 5 IP addresses during checkout. Later, once their account is provisioned, they could upgrade their configurable options beyond this limit. The limit would also not apply to staff. I wonder if this would make sense as an option to quantities only, or if there is a way to provide limits on other config option field types as well. * This needs further discussion *
              Hide
              Permalink
              cody Cody Phillips (Inactive) added a comment -

              A "Maximum" value a client may order, or upgrade to in the client area has been proposed. A use case are IP addresses. Hosting providers want to allow a client to order say up to 5 IP addresses during checkout. Later, once their account is provisioned, they could upgrade their configurable options beyond this limit. The limit would also not apply to staff.

              I wonder if this would make sense as an option to quantities only, or if there is a way to provide limits on other config option field types as well. This needs further discussion

              This doesn't apply to this task, so should be a separate task. All this information will, essentially, disappear when this task is completed.

              Show
              cody Cody Phillips (Inactive) added a comment - A "Maximum" value a client may order, or upgrade to in the client area has been proposed. A use case are IP addresses. Hosting providers want to allow a client to order say up to 5 IP addresses during checkout. Later, once their account is provisioned, they could upgrade their configurable options beyond this limit. The limit would also not apply to staff. I wonder if this would make sense as an option to quantities only, or if there is a way to provide limits on other config option field types as well. This needs further discussion This doesn't apply to this task, so should be a separate task. All this information will, essentially, disappear when this task is completed.
              cody Cody Phillips (Inactive) made changes -
              Field Original Value New Value
              Story Points 5
              cody Cody Phillips (Inactive) made changes -
              Rank Ranked higher
              cody Cody Phillips (Inactive) made changes -
              Link This issue blocks CORE-1447 [ CORE-1447 ]
              cody Cody Phillips (Inactive) made changes -
              Link This issue blocks CORE-1478 [ CORE-1478 ]
              admin Paul Phillips made changes -
              Fix Version/s 3.5.0 [ 10401 ]
              cody Cody Phillips (Inactive) made changes -
              Rank Ranked higher
              cody Cody Phillips (Inactive) made changes -
              Sprint 3.5.0 Sprint 1 [ 6 ]
              cody Cody Phillips (Inactive) made changes -
              Sprint 3.5.0 Sprint 1 [ 6 ] 3.5.0 Sprint 2 [ 10 ]
              cody Cody Phillips (Inactive) made changes -
              Rank Ranked higher
              cody Cody Phillips (Inactive) made changes -
              Sprint 3.5.0 Sprint 2 [ 10 ] 3.5.0 Sprint 1 [ 6 ]
              cody Cody Phillips (Inactive) made changes -
              Rank Ranked lower
              cody Cody Phillips (Inactive) made changes -
              Status Open [ 1 ] In Progress [ 3 ]
              cody Cody Phillips (Inactive) made changes -
              Status In Progress [ 3 ] Resolved [ 5 ]
              Resolution Fixed [ 1 ]
              tyson Tyson Phillips (Inactive) made changes -
              Link This issue blocks CORE-1545 [ CORE-1545 ]
              tyson Tyson Phillips (Inactive) made changes -
              Link This issue blocks CORE-1546 [ CORE-1546 ]
              tyson Tyson Phillips (Inactive) made changes -
              Status Resolved [ 5 ] Closed [ 6 ]

                People

                • Assignee:
                  cody Cody Phillips (Inactive)
                  Reporter:
                  admin Paul Phillips
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    7/Apr/15

                    Agile