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

            relates to

            Improvement - An improvement or enhancement to an existing feature or task. CORE-2174 Remove 'Staff' column from Module Logs table

            • Trivial - Cosmetic problem like misspelt words or misaligned text.
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. CORE-2154 Staff missing from module logs

            • Major - Major loss of function.
            • Closed

              Activity

              Descending order - Click to sort in ascending order
              Automated transition triggered when Tyson Phillips (Inactive) merged pull request #636 in Stash -
              Status In Review [ 5 ] Closed [ 6 ]
              jonathan Jonathan Reissmueller made changes -
              Time Spent 45 minutes [ 2700 ] 1 hour, 19 minutes [ 4740 ]
              Worklog Id 12093 [ 12093 ]
              tyson Tyson Phillips (Inactive) made changes -
              Remaining Estimate 0 minutes [ 0 ]
              Time Spent 45 minutes [ 2700 ]
              Worklog Id 12091 [ 12091 ]
              Automated transition triggered when Tyson Phillips (Inactive) created pull request #636 in Stash -
              Status In Progress [ 3 ] In Review [ 5 ]
              Resolution Fixed [ 1 ]
              tyson Tyson Phillips (Inactive) made changes -
              Status Open [ 1 ] In Progress [ 3 ]
              tyson Tyson Phillips (Inactive) made changes -
              Assignee Tyson Phillips [ tyson ]
              tyson Tyson Phillips (Inactive) made changes -
              Rank Ranked higher
              tyson Tyson Phillips (Inactive) made changes -
              Sprint 4.6.0 Sprint 2, 4.6.0 Sprint 3, 4.6.0 Sprint 6 [ 69, 79, 81 ] 4.6.0 Sprint 2, 4.6.0 Sprint 3, 4.6.0 Sprint 5 [ 69, 79, 83 ]
              tyson Tyson Phillips (Inactive) made changes -
              Rank Ranked lower
              tyson Tyson Phillips (Inactive) made changes -
              Sprint 4.6.0 Sprint 2, 4.6.0 Sprint 3, 4.6.0 Sprint 4 [ 69, 79, 80 ] 4.6.0 Sprint 2, 4.6.0 Sprint 3, 4.6.0 Sprint 5 [ 69, 79, 81 ]
              tyson Tyson Phillips (Inactive) made changes -
              Sprint 4.6.0 Sprint 2, 4.6.0 Sprint 3 [ 69, 79 ] 4.6.0 Sprint 2, 4.6.0 Sprint 3, 4.6.0 Sprint 4 [ 69, 79, 80 ]
              tyson Tyson Phillips (Inactive) made changes -
              Assignee Tyson Phillips [ tyson ]
              tyson Tyson Phillips (Inactive) made changes -
              Status In Progress [ 3 ] Open [ 1 ]
              tyson Tyson Phillips (Inactive) made changes -
              Rank Ranked higher
              tyson Tyson Phillips (Inactive) made changes -
              Sprint 4.6.0 Sprint 2 [ 69 ] 4.6.0 Sprint 2, 4.6.0 Sprint 3 [ 69, 79 ]
              tyson Tyson Phillips (Inactive) made changes -
              Assignee Tyson Phillips [ tyson ]
              tyson Tyson Phillips (Inactive) made changes -
              Fix Version/s 4.6.0-b1 [ 11117 ]
              Fix Version/s Short Term [ 10800 ]
              tyson Tyson Phillips (Inactive) made changes -
              Rank Ranked higher
              tyson Tyson Phillips (Inactive) made changes -
              Sprint 4.6.0 Sprint 2 [ 69 ]
              tyson Tyson Phillips (Inactive) made changes -
              Description Use the Requestor service to determine the staff ID (if available) and set it when module logs are saved.

              # 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
              # Update Logs::addModule to validate the given 'staff_id' represents a valid staff member in the system


              ----

              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.               		Use the Requestor service to determine the staff ID (if available) and set it when module logs are saved.

              # 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
              # Update Logs::addModule to validate the given 'staff_id' represents a valid staff member in the system
              # 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.
              tyson Tyson Phillips (Inactive) made changes -
              Story Points 2
              tyson Tyson Phillips (Inactive) made changes -
              Description 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.               		Use the Requestor service to determine the staff ID (if available) and set it when module logs are saved.

              # 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
              # Update Logs::addModule to validate the given 'staff_id' represents a valid staff member in the system


              ----

              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.
              Automated transition triggered when Cody Phillips (Inactive) made commit a25bc2b8746 in Stash -
              Status Reopened [ 4 ] In Progress [ 3 ]
              tyson Tyson Phillips (Inactive) made changes -
              Resolution Fixed [ 1 ]
              Status In Review [ 5 ] Reopened [ 4 ]
              Automated transition triggered when Tyson Phillips (Inactive) created pull request #121 in Stash -
              Status In Progress [ 3 ] In Review [ 5 ]
              Resolution Fixed [ 1 ]
              Automated transition triggered when Tyson Phillips (Inactive) made commit 2e3314021f2 in Stash -
              Status Open [ 1 ] In Progress [ 3 ]
              tyson Tyson Phillips (Inactive) made changes -
              Description 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.               		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.
              tyson Tyson Phillips (Inactive) made changes -
              Link This issue relates to CORE-2174 [ CORE-2174 ]
              tyson Tyson Phillips (Inactive) made changes -
              Field Original Value New Value
              Link This issue relates to CORE-2154 [ CORE-2154 ]
              tyson Tyson Phillips (Inactive) created 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