Details

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

      Description

      As part of GDPR, and data portability, customers may request and are entitled to an export of their data. While it may be worthwhile to provide the client a means of generating this data on their own, there is nothing wrong with having a staff member run the export and provide the data to the customer manually.

      It makes sense for this export to be included as a report, under Billing > Reports. The type should be JSON, so a new format of JSON should be added to the current and only CSV format.

      Format
      JSON

      Report Type
      Client Data Portability

      Client
      AJAX search for the client by name, or enter the Client ID.

      The resulting report should be a JSON formatted array of everything we have on this customer, including:

      • All services
      • All transactions
      • All invoices
      • All tickets (If Support Manager is installed)
      • All logins including IP address and time of login
      • All contacts (including primary contact/client)
      • All payment accounts (but not cc/ach encrypted data, just masked data like last 4, whatever we have that we don't have to decrypt)

      *Do not include any encrypted data*

        Issue Links

          Activity

          admin Paul Phillips created issue -
          admin Paul Phillips made changes -
          Field Original Value New Value
          Parent Issue CORE-2463 [ CORE-2463 ] CORE-2679 [ CORE-2679 ]
          admin Paul Phillips made changes -
          Description As part of GDPR, and data portability, customers may request and are entitled to an export of their data. While it may be worthwhile to provide the client a means of generating this data on their own, there is nothing wrong with having a staff member run the export and provide the data to the customer manually.

          It makes sense for this export to be included as a report, under Billing > Reports. The type should be JSON, so a new format of JSON should be added to the current and only CSV format.

          *Format*
          JSON

          *Report Type*
          Client Data Portability

          *Client*
          AJAX search for the client by name, or enter the Client ID.

          The resulting report should be a JSON formatted array of everything we have on this customer, including:

          * All services
          * All transactions
          * All invoices
          * All tickets (If Support Manager is installed)
          * All logins including IP address and time of login
          * All contacts (including primary contact/client)
          As part of GDPR, and data portability, customers may request and are entitled to an export of their data. While it may be worthwhile to provide the client a means of generating this data on their own, there is nothing wrong with having a staff member run the export and provide the data to the customer manually.

          It makes sense for this export to be included as a report, under Billing > Reports. The type should be JSON, so a new format of JSON should be added to the current and only CSV format.

          *Format*
          JSON

          *Report Type*
          Client Data Portability

          *Client*
          AJAX search for the client by name, or enter the Client ID.

          The resulting report should be a JSON formatted array of everything we have on this customer, including:

          * All services
          * All transactions
          * All invoices
          * All tickets (If Support Manager is installed)
          * All logins including IP address and time of login
          * All contacts (including primary contact/client)

          **Do not include any encrypted data**
          admin Paul Phillips made changes -
          Description As part of GDPR, and data portability, customers may request and are entitled to an export of their data. While it may be worthwhile to provide the client a means of generating this data on their own, there is nothing wrong with having a staff member run the export and provide the data to the customer manually.

          It makes sense for this export to be included as a report, under Billing > Reports. The type should be JSON, so a new format of JSON should be added to the current and only CSV format.

          *Format*
          JSON

          *Report Type*
          Client Data Portability

          *Client*
          AJAX search for the client by name, or enter the Client ID.

          The resulting report should be a JSON formatted array of everything we have on this customer, including:

          * All services
          * All transactions
          * All invoices
          * All tickets (If Support Manager is installed)
          * All logins including IP address and time of login
          * All contacts (including primary contact/client)

          **Do not include any encrypted data**
          As part of GDPR, and data portability, customers may request and are entitled to an export of their data. While it may be worthwhile to provide the client a means of generating this data on their own, there is nothing wrong with having a staff member run the export and provide the data to the customer manually.

          It makes sense for this export to be included as a report, under Billing > Reports. The type should be JSON, so a new format of JSON should be added to the current and only CSV format.

          *Format*
          JSON

          *Report Type*
          Client Data Portability

          *Client*
          AJAX search for the client by name, or enter the Client ID.

          The resulting report should be a JSON formatted array of everything we have on this customer, including:

          * All services
          * All transactions
          * All invoices
          * All tickets (If Support Manager is installed)
          * All logins including IP address and time of login
          * All contacts (including primary contact/client)
          * All payment accounts (but not cc/ach encrypted data, just masked data like last 4, whatever we have that we don't have to decrypt)

          **Do not include any encrypted data**
          tyson Tyson Phillips (Inactive) made changes -
          Parent CORE-2679 [ 13836 ]
          Issue Type Sub-task [ 5 ] Story [ 7 ]
          Story Points 13
          tyson Tyson Phillips (Inactive) made changes -
          Epic Link CORE-2463 [ 13555 ]
          tyson Tyson Phillips (Inactive) made changes -
          Sprint 4.3.0 Sprint 9 [ 60 ]
          tyson Tyson Phillips (Inactive) made changes -
          Rank Ranked lower
          tyson Tyson Phillips (Inactive) made changes -
          Assignee Tyson Phillips [ tyson ]
          Automated transition triggered when Jonathan Reissmueller created a branch in Stash -
          Status Open [ 1 ] In Progress [ 3 ]
          tyson Tyson Phillips (Inactive) made changes -
          Assignee Tyson Phillips [ tyson ] Jonathan Reissmueller [ jonathan ]
          tyson Tyson Phillips (Inactive) made changes -
          Link This issue blocks CORE-2703 [ CORE-2703 ]
          jonathan Jonathan Reissmueller made changes -
          Remaining Estimate 0 minutes [ 0 ]
          Time Spent 2 hours, 55 minutes [ 10500 ]
          Worklog Id 11184 [ 11184 ]
          Automated transition triggered when Tyson Phillips (Inactive) created pull request #453 in Stash -
          Status In Progress [ 3 ] In Review [ 5 ]
          Resolution Fixed [ 1 ]
          Automated transition triggered when Tyson Phillips (Inactive) merged pull request #453 in Stash -
          Status In Review [ 5 ] Closed [ 6 ]
          tyson Tyson Phillips (Inactive) made changes -
          Link This issue relates to CORE-3057 [ CORE-3057 ]

            People

            • Assignee:
              jonathan Jonathan Reissmueller
              Reporter:
              admin Paul Phillips
            • 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 - 2 days, 6 hours, 52 minutes Remaining Estimate - 53 minutes
                53m
                Logged:
                Time Spent - 2 days, 6 hours, 52 minutes Remaining Estimate - 53 minutes
                2d 6h 52m

                  Agile