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
-
Epic Link:
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
Paul Phillips
created issue -
Paul Phillips
made changes -
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** |
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 Phillips (Inactive)
made changes -
| Parent |
|
|
| Issue Type | Sub-task [ 5 ] | Story [ 7 ] |
| Story Points | 13 |
Tyson Phillips (Inactive)
made changes -
| Epic Link |
|
Tyson Phillips (Inactive)
made changes -
| Sprint | 4.3.0 Sprint 9 [ 60 ] |
Tyson Phillips (Inactive)
made changes -
| Rank | Ranked lower |
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 Phillips (Inactive)
made changes -
| Assignee | Tyson Phillips [ tyson ] | Jonathan Reissmueller [ jonathan ] |
Tyson Phillips (Inactive)
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 Phillips (Inactive)
made changes -
