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

          Activity

            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