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

Allow config option values to be marked inactive

        Details

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

          Description

          This task is concerned with changes to config option values where a value may change such that it no longer matches those in use by existing services. If a service is updated that used the old config option value, it will be set to another config option value because the original no longer exists.

          The proposed solution is to two-fold:

          1. When saving a config option, each (current) value must be checked to see if a service is using it. If a service does use it, we must display an error. No option value can be deleted, or changed, if it is in use by a service.
          2. Add a select option to choose the value's status (i.e. Active/Inactive). An inactive option value will not be displayed anywhere, except on the service to which it is already set. This will allow the existing option to be maintained if it is not explicitly changed by admin or client. Clients can still have the ability to upgrade to another config option value from an inactive one.

            Issue Links

            blocks

            New Feature - A new feature of the product, which has yet to be developed. CORE-1880 Allow a default option to be selected for configurable options

            • Major - Major loss of function.
            • Closed

            Improvement - An improvement or enhancement to an existing feature or task. CORE-2963 Config option field descriptions

            • Major - Major loss of function.
            • Closed

              Activity

              Ascending order - Click to sort in descending order
              tyson Tyson Phillips (Inactive) created issue -
              tyson Tyson Phillips (Inactive) made changes -
              Field Original Value New Value
              Description This task is concerned with changes to config option values where a value may change such that it no longer matches those in use by existing services. If a service is updated that used the old config option value, it will be set to another config option value because the original no longer exists.

              The proposed solution is to two-fold:
              # When saving a config option, each value must be checked to see if a service is using it. If a service does use it, we must display an error. No option value can be deleted if it is in use by a service.
              # Add a checkbox for each config option value to indicate it will be inactive. An inactive option value will not be displayed anywhere--except when displayed to admins. This will allow the existing option to be maintained if it is not explicitly changed by admin or client. Clients can still have the ability to upgrade to another config option from an inactive one.               		This task is concerned with changes to config option values where a value may change such that it no longer matches those in use by existing services. If a service is updated that used the old config option value, it will be set to another config option value because the original no longer exists.

              The proposed solution is to two-fold:
              # When saving a config option, each (current) value must be checked to see if a service is using it. If a service does use it, we must display an error. No option value can be deleted, or changed, if it is in use by a service.
              # Add a checkbox for each config option value to indicate it will be inactive. An inactive option value will not be displayed anywhere--except when displayed to admins. This will allow the existing option to be maintained if it is not explicitly changed by admin or client. Clients can still have the ability to upgrade to another config option from an inactive one.
              admin Paul Phillips made changes -
              Fix Version/s Short Term [ 10800 ]
              admin Paul Phillips made changes -
              Fix Version/s Sponsored [ 11113 ]
              Fix Version/s Short Term [ 10800 ]
              Hide
              Permalink
              admin Paul Phillips added a comment -

              Consider these scenarios:

              • A configurable option dropdown is used with the SolusVM module to select the OS template to install. This same dropdown controls the control panel used by a licensing plugin. Options cPanel and Plesk are present. We choose to stop offering Plesk but need to let people who already have it, keep it. Disabling the option for Plesk while allowing current customers to retain it would address this problem as new people would not be able to order it.
              • A similar situation with Litespeed Licenses. Lets cite VPS and Ultra VPS licenses which have now been replaced by things like “Web Host Lite”, “Web Host Pro” type things. Old licenses continue to work as Litespeed kept them functioning, but we want to move to the new options so we need to let current people swap to them if they want, but not force it, all while preventing new orders of the old types.
              Show
              admin Paul Phillips added a comment - Consider these scenarios: A configurable option dropdown is used with the SolusVM module to select the OS template to install. This same dropdown controls the control panel used by a licensing plugin. Options cPanel and Plesk are present. We choose to stop offering Plesk but need to let people who already have it, keep it. Disabling the option for Plesk while allowing current customers to retain it would address this problem as new people would not be able to order it. A similar situation with Litespeed Licenses. Lets cite VPS and Ultra VPS licenses which have now been replaced by things like “Web Host Lite”, “Web Host Pro” type things. Old licenses continue to work as Litespeed kept them functioning, but we want to move to the new options so we need to let current people swap to them if they want, but not force it, all while preventing new orders of the old types.
              tyson Tyson Phillips (Inactive) made changes -
              Rank Ranked higher
              tyson Tyson Phillips (Inactive) made changes -
              Rank Ranked lower
              tyson Tyson Phillips (Inactive) made changes -
              Story Points 8
              tyson Tyson Phillips (Inactive) made changes -
              Sprint 4.6.0 Sprint 4 [ 80 ]
              tyson Tyson Phillips (Inactive) made changes -
              Fix Version/s 4.6.0-b1 [ 11117 ]
              tyson Tyson Phillips (Inactive) made changes -
              Sprint 4.6.0 Sprint 4 [ 80 ] 4.6.0 Sprint 4, 4.6.0 Sprint 5 [ 80, 83 ]
              tyson Tyson Phillips (Inactive) made changes -
              Rank Ranked higher
              tyson Tyson Phillips (Inactive) made changes -
              Status Open [ 1 ] In Progress [ 3 ]
              tyson Tyson Phillips (Inactive) made changes -
              Remaining Estimate 0 minutes [ 0 ]
              Time Spent 53 minutes [ 3180 ]
              Worklog Id 12063 [ 12063 ]
              tyson Tyson Phillips (Inactive) made changes -
              Time Spent 53 minutes [ 3180 ] 3 hours, 19 minutes [ 11940 ]
              Worklog Id 12067 [ 12067 ]
              tyson Tyson Phillips (Inactive) made changes -
              Time Spent 3 hours, 19 minutes [ 11940 ] 7 hours, 3 minutes [ 25380 ]
              Worklog Id 12069 [ 12069 ]
              tyson Tyson Phillips (Inactive) made changes -
              Description This task is concerned with changes to config option values where a value may change such that it no longer matches those in use by existing services. If a service is updated that used the old config option value, it will be set to another config option value because the original no longer exists.

              The proposed solution is to two-fold:
              # When saving a config option, each (current) value must be checked to see if a service is using it. If a service does use it, we must display an error. No option value can be deleted, or changed, if it is in use by a service.
              # Add a checkbox for each config option value to indicate it will be inactive. An inactive option value will not be displayed anywhere--except when displayed to admins. This will allow the existing option to be maintained if it is not explicitly changed by admin or client. Clients can still have the ability to upgrade to another config option from an inactive one.               		This task is concerned with changes to config option values where a value may change such that it no longer matches those in use by existing services. If a service is updated that used the old config option value, it will be set to another config option value because the original no longer exists.

              The proposed solution is to two-fold:
              # When saving a config option, each (current) value must be checked to see if a service is using it. If a service does use it, we must display an error. No option value can be deleted, or changed, if it is in use by a service.
              # Add a checkbox for each config option value to indicate it will be inactive. An inactive option value will not be displayed anywhere--except when displayed to admins. This will allow the existing option to be maintained if it is not explicitly changed by admin or client. Clients can still have the ability to upgrade to another config option value from an inactive one.
              tyson Tyson Phillips (Inactive) made changes -
              Time Spent 7 hours, 3 minutes [ 25380 ] 1 day, 3 hours, 24 minutes [ 41040 ]
              Worklog Id 12075 [ 12075 ]
              tyson Tyson Phillips (Inactive) made changes -
              Time Spent 1 day, 3 hours, 24 minutes [ 41040 ] 1 day, 6 hours, 33 minutes [ 52380 ]
              Worklog Id 12077 [ 12077 ]
              tyson Tyson Phillips (Inactive) made changes -
              Link This issue blocks CORE-1880 [ CORE-1880 ]
              tyson Tyson Phillips (Inactive) made changes -
              Description This task is concerned with changes to config option values where a value may change such that it no longer matches those in use by existing services. If a service is updated that used the old config option value, it will be set to another config option value because the original no longer exists.

              The proposed solution is to two-fold:
              # When saving a config option, each (current) value must be checked to see if a service is using it. If a service does use it, we must display an error. No option value can be deleted, or changed, if it is in use by a service.
              # Add a checkbox for each config option value to indicate it will be inactive. An inactive option value will not be displayed anywhere--except when displayed to admins. This will allow the existing option to be maintained if it is not explicitly changed by admin or client. Clients can still have the ability to upgrade to another config option value from an inactive one.               		This task is concerned with changes to config option values where a value may change such that it no longer matches those in use by existing services. If a service is updated that used the old config option value, it will be set to another config option value because the original no longer exists.

              The proposed solution is to two-fold:
              # When saving a config option, each (current) value must be checked to see if a service is using it. If a service does use it, we must display an error. No option value can be deleted, or changed, if it is in use by a service.
              # Add a select option to choose the value's status (i.e. Active/Inactive). An inactive option value will not be displayed anywhere, except on the service to which it is already set. This will allow the existing option to be maintained if it is not explicitly changed by admin or client. Clients can still have the ability to upgrade to another config option value from an inactive one.
              Automated transition triggered when Tyson Phillips (Inactive) created pull request #634 in Stash -
              Status In Progress [ 3 ] In Review [ 5 ]
              Resolution Fixed [ 1 ]
              tyson Tyson Phillips (Inactive) made changes -
              Time Spent 1 day, 6 hours, 33 minutes [ 52380 ] 2 days, 4 hours, 13 minutes [ 72780 ]
              Worklog Id 12078 [ 12078 ]
              jonathan Jonathan Reissmueller made changes -
              Time Spent 2 days, 4 hours, 13 minutes [ 72780 ] 2 days, 6 hours, 12 minutes [ 79920 ]
              Worklog Id 12086 [ 12086 ]
              tyson Tyson Phillips (Inactive) made changes -
              Link This issue blocks CORE-2963 [ CORE-2963 ]
              Automated transition triggered when Tyson Phillips (Inactive) merged pull request #634 in Stash -
              Status In Review [ 5 ] Closed [ 6 ]

                People

                • Assignee:
                  tyson Tyson Phillips (Inactive)
                  Reporter:
                  tyson Tyson Phillips (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 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 - 2 days, 6 hours, 12 minutes
                    2d 6h 12m

                      Agile