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

      Create a new report under Billing > Reports called the Client Data Portability report. This should be named internally under /reports/client_data/client_data.php.

      This report should support the new JSON format for reports (CORE-2688).

      The report needs to accept a client ID as a filter option (it must be given). If possible an auto-complete feature to search for the client and set the ID in the form dynamically would be a nice addition.

      The report must return ALL client-related information within reason, excluding encrypted data, data not personally identifiable, irrelevant (e.g. system-level data), or of other resources (e.g. files).

      1. Contacts
        • Users
      2. Services
        • Service meta data (not encrypted data)
      3. Invoices
        • Invoice line items
      4. Transactions
        • Transactions applied to invoices?
      5. Logs
        • User log in logs
        • Contact update logs
        • Not email logs (they should have already received the email)
      6. Payment accounts (not encrypted fields)
      7. Plugin information (must call the Report.clientData event for all plugins)
        • The plugin information should probably be appended to the dataset keyed as "_plu" concatenanted with the plugin ID, and the value would be the data retrievewed by the plugin

        Issue Links

          Activity

          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 -
          Link This issue is blocked by CORE-2688 [ CORE-2688 ]
          tyson Tyson Phillips (Inactive) made changes -
          Link This issue is blocked by CORE-2689 [ CORE-2689 ]
          tyson Tyson Phillips (Inactive) made changes -
          Description Create a new report under *Billing > Reports* called the _Client Data Portability_ report.

          This report should support the new JSON format for reports (CORE-2688).

          The report needs to accept a client ID as a filter option (it must be given). If possible an auto-complete feature to search for the client and set the ID in the form dynamically would be a nice addition.

          The report must return ALL client-related information within reason, excluding encrypted data, data not personally identifiable, irrelevant (e.g. system-level data), or of other resources (e.g. files).
          # Services
          #* Service meta data (not encrypted data)
          # Invoices
          #* Invoice line items
          # Transactions
          #* Transactions applied to invoices?
          # Logs
          #* User log in logs
          #* Contact update logs
          #* Not email logs (they should have already received the email)
          # Payment accounts (not encrypted fields)
          # Plugin information (must call the Cliens.export event for all plugins)
          #* The plugin information should probably be appended to the dataset keyed as "_ext" concatenanted with the plugin ID, and the value would be the data retrievewed by the plugin
          Create a new report under *Billing > Reports* called the _Client Data Portability_ report.

          This report should support the new JSON format for reports (CORE-2688).

          The report needs to accept a client ID as a filter option (it must be given). If possible an auto-complete feature to search for the client and set the ID in the form dynamically would be a nice addition.

          The report must return ALL client-related information within reason, excluding encrypted data, data not personally identifiable, irrelevant (e.g. system-level data), or of other resources (e.g. files).
          # Services
          #* Service meta data (not encrypted data)
          # Invoices
          #* Invoice line items
          # Transactions
          #* Transactions applied to invoices?
          # Logs
          #* User log in logs
          #* Contact update logs
          #* Not email logs (they should have already received the email)
          # Payment accounts (not encrypted fields)
          # Plugin information (must call the Cliens.export event for all plugins)
          #* The plugin information should probably be appended to the dataset keyed as "_plu" concatenanted with the plugin ID, and the value would be the data retrievewed by the plugin
          jonathan Jonathan Reissmueller made changes -
          Description Create a new report under *Billing > Reports* called the _Client Data Portability_ report.

          This report should support the new JSON format for reports (CORE-2688).

          The report needs to accept a client ID as a filter option (it must be given). If possible an auto-complete feature to search for the client and set the ID in the form dynamically would be a nice addition.

          The report must return ALL client-related information within reason, excluding encrypted data, data not personally identifiable, irrelevant (e.g. system-level data), or of other resources (e.g. files).
          # Services
          #* Service meta data (not encrypted data)
          # Invoices
          #* Invoice line items
          # Transactions
          #* Transactions applied to invoices?
          # Logs
          #* User log in logs
          #* Contact update logs
          #* Not email logs (they should have already received the email)
          # Payment accounts (not encrypted fields)
          # Plugin information (must call the Cliens.export event for all plugins)
          #* The plugin information should probably be appended to the dataset keyed as "_plu" concatenanted with the plugin ID, and the value would be the data retrievewed by the plugin
          Create a new report under *Billing > Reports* called the _Client Data Portability_ report.

          This report should support the new JSON format for reports (CORE-2688).

          The report needs to accept a client ID as a filter option (it must be given). If possible an auto-complete feature to search for the client and set the ID in the form dynamically would be a nice addition.

          The report must return ALL client-related information within reason, excluding encrypted data, data not personally identifiable, irrelevant (e.g. system-level data), or of other resources (e.g. files).
          # Client
          # Contact
          # Services
          #* Service meta data (not encrypted data)
          # Invoices
          #* Invoice line items
          # Transactions
          #* Transactions applied to invoices?
          # Logs
          #* User log in logs
          #* Contact update logs
          #* Not email logs (they should have already received the email)
          # Payment accounts (not encrypted fields)
          # Plugin information (must call the Cliens.export event for all plugins)
          #* The plugin information should probably be appended to the dataset keyed as "_plu" concatenanted with the plugin ID, and the value would be the data retrievewed by the plugin
          jonathan Jonathan Reissmueller made changes -
          Description Create a new report under *Billing > Reports* called the _Client Data Portability_ report.

          This report should support the new JSON format for reports (CORE-2688).

          The report needs to accept a client ID as a filter option (it must be given). If possible an auto-complete feature to search for the client and set the ID in the form dynamically would be a nice addition.

          The report must return ALL client-related information within reason, excluding encrypted data, data not personally identifiable, irrelevant (e.g. system-level data), or of other resources (e.g. files).
          # Client
          # Contact
          # Services
          #* Service meta data (not encrypted data)
          # Invoices
          #* Invoice line items
          # Transactions
          #* Transactions applied to invoices?
          # Logs
          #* User log in logs
          #* Contact update logs
          #* Not email logs (they should have already received the email)
          # Payment accounts (not encrypted fields)
          # Plugin information (must call the Cliens.export event for all plugins)
          #* The plugin information should probably be appended to the dataset keyed as "_plu" concatenanted with the plugin ID, and the value would be the data retrievewed by the plugin
          Create a new report under *Billing > Reports* called the _Client Data Portability_ report.

          This report should support the new JSON format for reports (CORE-2688).

          The report needs to accept a client ID as a filter option (it must be given). If possible an auto-complete feature to search for the client and set the ID in the form dynamically would be a nice addition.

          The report must return ALL client-related information within reason, excluding encrypted data, data not personally identifiable, irrelevant (e.g. system-level data), or of other resources (e.g. files).
          # Client
          #* Users
          #* Contacts
          # Services
          #* Service meta data (not encrypted data)
          # Invoices
          #* Invoice line items
          # Transactions
          #* Transactions applied to invoices?
          # Logs
          #* User log in logs
          #* Contact update logs
          #* Not email logs (they should have already received the email)
          # Payment accounts (not encrypted fields)
          # Plugin information (must call the Cliens.export event for all plugins)
          #* The plugin information should probably be appended to the dataset keyed as "_plu" concatenanted with the plugin ID, and the value would be the data retrievewed by the plugin
          jonathan Jonathan Reissmueller made changes -
          Description Create a new report under *Billing > Reports* called the _Client Data Portability_ report.

          This report should support the new JSON format for reports (CORE-2688).

          The report needs to accept a client ID as a filter option (it must be given). If possible an auto-complete feature to search for the client and set the ID in the form dynamically would be a nice addition.

          The report must return ALL client-related information within reason, excluding encrypted data, data not personally identifiable, irrelevant (e.g. system-level data), or of other resources (e.g. files).
          # Client
          #* Users
          #* Contacts
          # Services
          #* Service meta data (not encrypted data)
          # Invoices
          #* Invoice line items
          # Transactions
          #* Transactions applied to invoices?
          # Logs
          #* User log in logs
          #* Contact update logs
          #* Not email logs (they should have already received the email)
          # Payment accounts (not encrypted fields)
          # Plugin information (must call the Cliens.export event for all plugins)
          #* The plugin information should probably be appended to the dataset keyed as "_plu" concatenanted with the plugin ID, and the value would be the data retrievewed by the plugin
          Create a new report under *Billing > Reports* called the _Client Data Portability_ report.

          This report should support the new JSON format for reports (CORE-2688).

          The report needs to accept a client ID as a filter option (it must be given). If possible an auto-complete feature to search for the client and set the ID in the form dynamically would be a nice addition.

          The report must return ALL client-related information within reason, excluding encrypted data, data not personally identifiable, irrelevant (e.g. system-level data), or of other resources (e.g. files).
          # Contacts
          #* Users
          # Services
          #* Service meta data (not encrypted data)
          # Invoices
          #* Invoice line items
          # Transactions
          #* Transactions applied to invoices?
          # Logs
          #* User log in logs
          #* Contact update logs
          #* Not email logs (they should have already received the email)
          # Payment accounts (not encrypted fields)
          # Plugin information (must call the Cliens.export event for all plugins)
          #* The plugin information should probably be appended to the dataset keyed as "_plu" concatenanted with the plugin ID, and the value would be the data retrievewed by the plugin
          tyson Tyson Phillips (Inactive) made changes -
          Description Create a new report under *Billing > Reports* called the _Client Data Portability_ report.

          This report should support the new JSON format for reports (CORE-2688).

          The report needs to accept a client ID as a filter option (it must be given). If possible an auto-complete feature to search for the client and set the ID in the form dynamically would be a nice addition.

          The report must return ALL client-related information within reason, excluding encrypted data, data not personally identifiable, irrelevant (e.g. system-level data), or of other resources (e.g. files).
          # Contacts
          #* Users
          # Services
          #* Service meta data (not encrypted data)
          # Invoices
          #* Invoice line items
          # Transactions
          #* Transactions applied to invoices?
          # Logs
          #* User log in logs
          #* Contact update logs
          #* Not email logs (they should have already received the email)
          # Payment accounts (not encrypted fields)
          # Plugin information (must call the Cliens.export event for all plugins)
          #* The plugin information should probably be appended to the dataset keyed as "_plu" concatenanted with the plugin ID, and the value would be the data retrievewed by the plugin
          Create a new report under *Billing > Reports* called the _Client Data Portability_ report. This should be named internally under /reports/client_data/client_data.php.

          This report should support the new JSON format for reports (CORE-2688).

          The report needs to accept a client ID as a filter option (it must be given). If possible an auto-complete feature to search for the client and set the ID in the form dynamically would be a nice addition.

          The report must return ALL client-related information within reason, excluding encrypted data, data not personally identifiable, irrelevant (e.g. system-level data), or of other resources (e.g. files).
          # Contacts
          #* Users
          # Services
          #* Service meta data (not encrypted data)
          # Invoices
          #* Invoice line items
          # Transactions
          #* Transactions applied to invoices?
          # Logs
          #* User log in logs
          #* Contact update logs
          #* Not email logs (they should have already received the email)
          # Payment accounts (not encrypted fields)
          # Plugin information (must call the *Report.clientData* event for all plugins)
          #* The plugin information should probably be appended to the dataset keyed as "_plu" concatenanted with the plugin ID, and the value would be the data retrievewed by the plugin
          jonathan Jonathan Reissmueller made changes -
          Remaining Estimate 0 minutes [ 0 ]
          Time Spent 2 hours, 28 minutes [ 8880 ]
          Worklog Id 11181 [ 11181 ]
          jonathan Jonathan Reissmueller made changes -
          Remaining Estimate 0 minutes [ 0 ] 2 hours, 28 minutes [ 8880 ]
          Time Spent 2 hours, 28 minutes [ 8880 ] 0 minutes [ 0 ]
          Worklog Id 11181 [ 11181 ]
          Worklog Time Spent 2 hours, 28 minutes [ 8880 ]
          Automated transition triggered when Jonathan Reissmueller created a branch in Stash -
          Status Open [ 1 ] In Progress [ 3 ]
          jonathan Jonathan Reissmueller made changes -
          Remaining Estimate 2 hours, 28 minutes [ 8880 ] 1 hour, 43 minutes [ 6180 ]
          Time Spent 0 minutes [ 0 ] 45 minutes [ 2700 ]
          Worklog Id 11190 [ 11190 ]
          Automated transition triggered when Jonathan Reissmueller created pull request #450 in Stash -
          Status In Progress [ 3 ] In Review [ 5 ]
          Resolution Fixed [ 1 ]
          jonathan Jonathan Reissmueller made changes -
          Assignee Jonathan Reissmueller [ jonathan ]
          jonathan Jonathan Reissmueller made changes -
          Remaining Estimate 1 hour, 43 minutes [ 6180 ] 53 minutes [ 3180 ]
          Time Spent 45 minutes [ 2700 ] 1 hour, 35 minutes [ 5700 ]
          Worklog Id 11193 [ 11193 ]
          Automated transition triggered when Tyson Phillips (Inactive) merged pull request #450 in Stash -
          Status In Review [ 5 ] Closed [ 6 ]
          tyson Tyson Phillips (Inactive) made changes -
          Link This issue Testing discovered CORE-2712 [ CORE-2712 ]

            People

            • Assignee:
              jonathan Jonathan Reissmueller
              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:
                Time Spent - 1 hour, 35 minutes Remaining Estimate - 53 minutes
                53m
                Logged:
                Time Spent - 1 hour, 35 minutes Remaining Estimate - 53 minutes
                1h 35m

                  Agile