Uploaded image for project: 'mod-audit'
  1. mod-audit
  2. MODAUD-12

Prepare DB tables for Circulation Audit Logs

    XMLWordPrintable

Details

    • Story
    • Status: Closed (View Workflow)
    • P3
    • Resolution: Done
    • None
    • 0.0.4
    • None
    • Firebird Sprint 95
    • 3
    • Firebird

    Description

      In order to save log entries DB ecosystem should be prepared in the mod-audit. Tables should be created for each object: loans, feesFines, itemBlock, patronBlock, manualBlock, request.

      Acceptance criteria:
      1) Tables for loans, feesFines, itemBlock, patronBlock, manualBlock, request created
      2) Tables structure corresponds Circulation Audit Logs

      TestRail: Results

        Attachments

          Issue Links

            defines

            New Feature - New feature requests UXPROD-1703 Circulation log of all actions filtered by a patron and/or a item with additional filters

            • TBD - To be determined
            • Closed
            has to be done before

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODAUD-10 GET /audit-data/logs for Circulation Audit Logs

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODAUD-15 LogEventListener for mod-audit

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Activity

              People

                khandramai Viachaslau Khandramai
                khandramai Viachaslau Khandramai
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases