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

Allow for a staff ID to be set for module for logging purposes

    Details

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

      Description

      Use the Requestor service to determine the staff ID (if available) and set it when module logs are saved.

      1. Wherever module logs are saved (ModuleManager and Module component classes), set the 'staff_id' to save for the log
        • The 'staff_id' can be determined from the Requestor service, if available
      2. Update Logs::addModule to validate the given 'staff_id' represents a valid staff member in the system
      3. Re-add the "Staff" column to the Tools > Logs > Module table

      Currently, module logs do not log any staff user that performed a module action. This is because modules are unaware of a staff user and because the abstract Module class does not provide a way to set one.

      The abstract Module class should be updated, similar to the abstract Gateway class, to add a setStaffId method. This should then be called on module objects to set a staff Id, if one is known in such instances.

      Then, a Staff column should be added to the module logs table under [Logs], to list the first and last name of the staff member that performed the action. Just uncomment the column in the admin_tools_logmodule template.

        Issue Links

          Activity

          There are no comments yet on this issue.

            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:
                28/May/19

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 hour, 19 minutes
                1h 19m

                  Agile