Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-2679 Add opt-in support for marketing emails
  3. CORE-2692

Create a new log for client settings

        Details

        • Type: Sub-task
        • Status: Closed
        • Priority: Major
        • Resolution: Fixed
        • Affects Version/s: None
        • Fix Version/s: 4.3.0-b1
        • Component/s: Staff Interface
        • Labels:
          None

          Description

          1. Add a new table, `log_client_settings`
            id client_id by_user_id ip_address change date_changed
            unsigned int(10) auto-increment primary key unsigned int(10) client ID updated unsigned int(10) NULLABLE, user ID that performed the action (of the staff or client or contact) varchar(39) NULLABLE, the IP of the user that performed the action json-encoded or base64-encoded serialized array of fields? (see below for example) datetime the time the record was inserted

          Set separate indexes for the following:

          • client_id set an INDEX
          • by_user_id set an INDEX
          • date_changed set an INDEX

          Changes should store a set of before/after key/value pairs from a set of client settings. This should be similar to Logs::addContact

          • An array of data keyed by the field name, each containing the keys 'prev' and 'cur' referencing the old value and the new value.
          • The data in this field should be (JSON-encoded or base64-encoded serialized strings similar to the contacts log?)
          1. There should exist a method by which to create a log entry for the client
          2. There should exist a method by which to delete the logs
            • Filter options should support any of the following
              • Client ID - delete all logs by this client
              • Date Changed - delete all logs older than the given date
            • The filter should also filter by the currently-configured company. i.e., only delete logs for the current company

            Issue Links

            blocks

            Sub-task - The sub-task of the issue CORE-2693 Integrate logging for client settings

            • Major - Major loss of function.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. CORE-2694 Create new tab to display client setting logs

            • Major - Major loss of function.
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. CORE-2726 Order client creation does not include IP address in client setting log

            • 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
              Component/s Staff Interface [ 10000 ]
              tyson Tyson Phillips (Inactive) made changes -
              Summary Create a new log for clients Create a new log for client settings
              tyson Tyson Phillips (Inactive) made changes -
              Description # Add a new table, `log_clients`
              ||id||client_id||by_user_id||ip_address||change||date_changed||
              |unsigned int(10) auto-increment primary key|client ID updated|user ID that performed the action (of the staff or client or contact)|varchar(39) the IP of the user that performed the action|base64-encoded serialized array of fields (see below for example)|datetime the time the record was inserted|

              Changes should store a set of before/after key/value pairs from a set of client fields/settings. This should be similar to Logs::addContact
              * An array of data keyed by the field name, each containing the keys 'prev' and 'cur' referencing the old value and the new value.

              # There should exist a method by which to create a log entry for the client
              # There should exist a method by which to delete the logs
              #* Filter options should support any of the following
              #** Client ID - delete all logs by this client
              #** Date Changed - delete all logs older than the given date
              #* The filter should also filter by the currently-configured company. i.e., only delete logs for the current company               		# Add a new table, `log_client_settings`
              ||id||client_id||by_user_id||ip_address||change||date_changed||
              |unsigned int(10) auto-increment primary key|client ID updated|user ID that performed the action (of the staff or client or contact)|varchar(39) the IP of the user that performed the action|base64-encoded serialized array of fields (see below for example)|datetime the time the record was inserted|

              Changes should store a set of before/after key/value pairs from a set of client fields/settings. This should be similar to Logs::addContact
              * An array of data keyed by the field name, each containing the keys 'prev' and 'cur' referencing the old value and the new value.

              # There should exist a method by which to create a log entry for the client
              # There should exist a method by which to delete the logs
              #* Filter options should support any of the following
              #** Client ID - delete all logs by this client
              #** Date Changed - delete all logs older than the given date
              #* The filter should also filter by the currently-configured company. i.e., only delete logs for the current company
              tyson Tyson Phillips (Inactive) made changes -
              Description # Add a new table, `log_client_settings`
              ||id||client_id||by_user_id||ip_address||change||date_changed||
              |unsigned int(10) auto-increment primary key|client ID updated|user ID that performed the action (of the staff or client or contact)|varchar(39) the IP of the user that performed the action|base64-encoded serialized array of fields (see below for example)|datetime the time the record was inserted|

              Changes should store a set of before/after key/value pairs from a set of client fields/settings. This should be similar to Logs::addContact
              * An array of data keyed by the field name, each containing the keys 'prev' and 'cur' referencing the old value and the new value.

              # There should exist a method by which to create a log entry for the client
              # There should exist a method by which to delete the logs
              #* Filter options should support any of the following
              #** Client ID - delete all logs by this client
              #** Date Changed - delete all logs older than the given date
              #* The filter should also filter by the currently-configured company. i.e., only delete logs for the current company               		# Add a new table, `log_client_settings`
              ||id||client_id||by_user_id||ip_address||change||date_changed||
              |unsigned int(10) auto-increment primary key|client ID updated|user ID that performed the action (of the staff or client or contact)|varchar(39) the IP of the user that performed the action|base64-encoded serialized array of fields (see below for example)|datetime the time the record was inserted|

              Changes should store a set of before/after key/value pairs from a set of client settings. This should be similar to Logs::addContact
              * An array of data keyed by the field name, each containing the keys 'prev' and 'cur' referencing the old value and the new value.

              # There should exist a method by which to create a log entry for the client
              # There should exist a method by which to delete the logs
              #* Filter options should support any of the following
              #** Client ID - delete all logs by this client
              #** Date Changed - delete all logs older than the given date
              #* The filter should also filter by the currently-configured company. i.e., only delete logs for the current company
              tyson Tyson Phillips (Inactive) made changes -
              Description # Add a new table, `log_client_settings`
              ||id||client_id||by_user_id||ip_address||change||date_changed||
              |unsigned int(10) auto-increment primary key|client ID updated|user ID that performed the action (of the staff or client or contact)|varchar(39) the IP of the user that performed the action|base64-encoded serialized array of fields (see below for example)|datetime the time the record was inserted|

              Changes should store a set of before/after key/value pairs from a set of client settings. This should be similar to Logs::addContact
              * An array of data keyed by the field name, each containing the keys 'prev' and 'cur' referencing the old value and the new value.

              # There should exist a method by which to create a log entry for the client
              # There should exist a method by which to delete the logs
              #* Filter options should support any of the following
              #** Client ID - delete all logs by this client
              #** Date Changed - delete all logs older than the given date
              #* The filter should also filter by the currently-configured company. i.e., only delete logs for the current company               		# Add a new table, `log_client_settings`
              ||id||client_id||by_user_id||ip_address||change||date_changed||
              |unsigned int(10) auto-increment primary key|unsigned int(10) client ID updated|unsigned int(10) NULLABLE, user ID that performed the action (of the staff or client or contact)|varchar(39) NULLABLE, the IP of the user that performed the action|base64-encoded serialized array of fields (see below for example)|datetime the time the record was inserted|

              Set separate indexes for the following:
              * _client_id_ set an INDEX
              * _by_user_id_ set an INDEX
              * _date_changed_ set an INDEX

              Changes should store a set of before/after key/value pairs from a set of client settings. This should be similar to Logs::addContact
              * An array of data keyed by the field name, each containing the keys 'prev' and 'cur' referencing the old value and the new value.
              * The data in this field should be base64-encoded serialized strings

              # There should exist a method by which to create a log entry for the client
              # There should exist a method by which to delete the logs
              #* Filter options should support any of the following
              #** Client ID - delete all logs by this client
              #** Date Changed - delete all logs older than the given date
              #* The filter should also filter by the currently-configured company. i.e., only delete logs for the current company
              tyson Tyson Phillips (Inactive) made changes -
              Link This issue blocks CORE-2693 [ CORE-2693 ]
              tyson Tyson Phillips (Inactive) made changes -
              Link This issue blocks CORE-2694 [ CORE-2694 ]
              tyson Tyson Phillips (Inactive) made changes -
              Description # Add a new table, `log_client_settings`
              ||id||client_id||by_user_id||ip_address||change||date_changed||
              |unsigned int(10) auto-increment primary key|unsigned int(10) client ID updated|unsigned int(10) NULLABLE, user ID that performed the action (of the staff or client or contact)|varchar(39) NULLABLE, the IP of the user that performed the action|base64-encoded serialized array of fields (see below for example)|datetime the time the record was inserted|

              Set separate indexes for the following:
              * _client_id_ set an INDEX
              * _by_user_id_ set an INDEX
              * _date_changed_ set an INDEX

              Changes should store a set of before/after key/value pairs from a set of client settings. This should be similar to Logs::addContact
              * An array of data keyed by the field name, each containing the keys 'prev' and 'cur' referencing the old value and the new value.
              * The data in this field should be base64-encoded serialized strings

              # There should exist a method by which to create a log entry for the client
              # There should exist a method by which to delete the logs
              #* Filter options should support any of the following
              #** Client ID - delete all logs by this client
              #** Date Changed - delete all logs older than the given date
              #* The filter should also filter by the currently-configured company. i.e., only delete logs for the current company               		# Add a new table, `log_client_settings`
              ||id||client_id||by_user_id||ip_address||change||date_changed||
              |unsigned int(10) auto-increment primary key|unsigned int(10) client ID updated|unsigned int(10) NULLABLE, user ID that performed the action (of the staff or client or contact)|varchar(39) NULLABLE, the IP of the user that performed the action|json-encoded or base64-encoded serialized array of fields? (see below for example)|datetime the time the record was inserted|

              Set separate indexes for the following:
              * _client_id_ set an INDEX
              * _by_user_id_ set an INDEX
              * _date_changed_ set an INDEX

              Changes should store a set of before/after key/value pairs from a set of client settings. This should be similar to Logs::addContact
              * An array of data keyed by the field name, each containing the keys 'prev' and 'cur' referencing the old value and the new value.
              * The data in this field should be base64-encoded serialized strings

              # There should exist a method by which to create a log entry for the client
              # There should exist a method by which to delete the logs
              #* Filter options should support any of the following
              #** Client ID - delete all logs by this client
              #** Date Changed - delete all logs older than the given date
              #* The filter should also filter by the currently-configured company. i.e., only delete logs for the current company
              tyson Tyson Phillips (Inactive) made changes -
              Description # Add a new table, `log_client_settings`
              ||id||client_id||by_user_id||ip_address||change||date_changed||
              |unsigned int(10) auto-increment primary key|unsigned int(10) client ID updated|unsigned int(10) NULLABLE, user ID that performed the action (of the staff or client or contact)|varchar(39) NULLABLE, the IP of the user that performed the action|json-encoded or base64-encoded serialized array of fields? (see below for example)|datetime the time the record was inserted|

              Set separate indexes for the following:
              * _client_id_ set an INDEX
              * _by_user_id_ set an INDEX
              * _date_changed_ set an INDEX

              Changes should store a set of before/after key/value pairs from a set of client settings. This should be similar to Logs::addContact
              * An array of data keyed by the field name, each containing the keys 'prev' and 'cur' referencing the old value and the new value.
              * The data in this field should be base64-encoded serialized strings

              # There should exist a method by which to create a log entry for the client
              # There should exist a method by which to delete the logs
              #* Filter options should support any of the following
              #** Client ID - delete all logs by this client
              #** Date Changed - delete all logs older than the given date
              #* The filter should also filter by the currently-configured company. i.e., only delete logs for the current company               		# Add a new table, `log_client_settings`
              ||id||client_id||by_user_id||ip_address||change||date_changed||
              |unsigned int(10) auto-increment primary key|unsigned int(10) client ID updated|unsigned int(10) NULLABLE, user ID that performed the action (of the staff or client or contact)|varchar(39) NULLABLE, the IP of the user that performed the action|json-encoded or base64-encoded serialized array of fields? (see below for example)|datetime the time the record was inserted|

              Set separate indexes for the following:
              * _client_id_ set an INDEX
              * _by_user_id_ set an INDEX
              * _date_changed_ set an INDEX

              Changes should store a set of before/after key/value pairs from a set of client settings. This should be similar to Logs::addContact
              * An array of data keyed by the field name, each containing the keys 'prev' and 'cur' referencing the old value and the new value.
              * The data in this field should be (JSON-encoded or base64-encoded serialized strings similar to the contacts log?)

              # There should exist a method by which to create a log entry for the client
              # There should exist a method by which to delete the logs
              #* Filter options should support any of the following
              #** Client ID - delete all logs by this client
              #** Date Changed - delete all logs older than the given date
              #* The filter should also filter by the currently-configured company. i.e., only delete logs for the current company
              Automated transition triggered when Tyson Phillips (Inactive) created a branch in Stash -
              Status Open [ 1 ] In Progress [ 3 ]
              tyson Tyson Phillips (Inactive) made changes -
              Assignee Tyson Phillips [ tyson ]
              tyson Tyson Phillips (Inactive) made changes -
              Remaining Estimate 0 minutes [ 0 ]
              Time Spent 29 minutes [ 1740 ]
              Worklog Id 11105 [ 11105 ]
              tyson Tyson Phillips (Inactive) made changes -
              Description # Add a new table, `log_client_settings`
              ||id||client_id||by_user_id||ip_address||change||date_changed||
              |unsigned int(10) auto-increment primary key|unsigned int(10) client ID updated|unsigned int(10) NULLABLE, user ID that performed the action (of the staff or client or contact)|varchar(39) NULLABLE, the IP of the user that performed the action|json-encoded or base64-encoded serialized array of fields? (see below for example)|datetime the time the record was inserted|

              Set separate indexes for the following:
              * _client_id_ set an INDEX
              * _by_user_id_ set an INDEX
              * _date_changed_ set an INDEX

              Changes should store a set of before/after key/value pairs from a set of client settings. This should be similar to Logs::addContact
              * An array of data keyed by the field name, each containing the keys 'prev' and 'cur' referencing the old value and the new value.
              * The data in this field should be (JSON-encoded or base64-encoded serialized strings similar to the contacts log?)

              # There should exist a method by which to create a log entry for the client
              # There should exist a method by which to delete the logs
              #* Filter options should support any of the following
              #** Client ID - delete all logs by this client
              #** Date Changed - delete all logs older than the given date
              #* The filter should also filter by the currently-configured company. i.e., only delete logs for the current company               		# Add a new table, `log_client_settings`
              ||id||client_id||by_user_id||ip_address||change||date_changed||
              |unsigned int(10) auto-increment primary key|unsigned int(10) client ID updated|unsigned int(10) NULLABLE, user ID that performed the action (of the staff or client or contact)|varchar(39) NULLABLE, the IP of the user that performed the action|-json-encoded- or base64-encoded serialized array of fields? (see below for example)|datetime the time the record was inserted|

              Set separate indexes for the following:
              * _client_id_ set an INDEX
              * _by_user_id_ set an INDEX
              * _date_changed_ set an INDEX

              Changes should store a set of before/after key/value pairs from a set of client settings. This should be similar to Logs::addContact
              * An array of data keyed by the field name, each containing the keys 'prev' and 'cur' referencing the old value and the new value.
              * The data in this field should be (-JSON-encoded or- base64-encoded serialized strings similar to the contacts log?)

              # There should exist a method by which to create a log entry for the client
              # There should exist a method by which to delete the logs
              #* Filter options should support any of the following
              #** Client ID - delete all logs by this client
              #** Date Changed - delete all logs older than the given date
              #* The filter should also filter by the currently-configured company. i.e., only delete logs for the current company
              Automated transition triggered when Tyson Phillips (Inactive) created pull request #440 in Stash -
              Status In Progress [ 3 ] In Review [ 5 ]
              Resolution Fixed [ 1 ]
              Automated transition triggered when Tyson Phillips (Inactive) merged pull request #440 in Stash -
              Status In Review [ 5 ] Closed [ 6 ]
              tyson Tyson Phillips (Inactive) made changes -
              Resolution Fixed [ 1 ]
              Status Closed [ 6 ] Reopened [ 4 ]
              tyson Tyson Phillips (Inactive) made changes -
              Time Spent 29 minutes [ 1740 ] 3 hours, 12 minutes [ 11520 ]
              Worklog Id 11115 [ 11115 ]
              tyson Tyson Phillips (Inactive) made changes -
              Status Reopened [ 4 ] Closed [ 6 ]
              Resolution Fixed [ 1 ]
              tyson Tyson Phillips (Inactive) made changes -
              Link This issue relates to CORE-2726 [ CORE-2726 ]

                People

                • Assignee:
                  tyson Tyson Phillips (Inactive)
                  Reporter:
                  tyson Tyson Phillips (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    15/Jun/18

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 3 hours, 12 minutes
                    3h 12m

                      Agile