Update Kibana-Reporting-Design-Proposal.md

docs/dev/Kibana-Reporting-Design-Proposal.md

@@ -54,6 +54,7 @@ Kibana Reports for Open Distro allows ‘Report Owner’ (engineers, including b
 1. As a user, I should see Name, Type, Owner, Source, Last updated, Details, Status (active/disabled) on the `Report definitions` list.
 1. As a user, I should be able to view, edit and delete a report definition.
 1. As a user, I should be able to enable/disable a report definition
+1. As a user, I should be able to export and import one or more report definitions (as xml or some other format) via APIs
 
 ### Create, View, Edit
 #### Create report definition
@@ -110,6 +111,7 @@ Kibana Reports for Open Distro allows ‘Report Owner’ (engineers, including b
 1. As a user, I should be able to archive an existing report. (p2)
 1. As a user, I should be able to downlaod available report files (PDF, PNG, CSV, Excel, etc)
 1. As a user, I should be able to copy the permalink to a report source.
+1. As a user, I should be able to view the report shared with me via email as an embedded HTML.
 
 ##### Sharing or archiving an existing report
 1. As a report owner, I should be able to share or archive a report.
@@ -120,6 +122,7 @@ Kibana Reports for Open Distro allows ‘Report Owner’ (engineers, including b
 1. As a report recepient, I can only archive a report.
 
 
+
 ### Functional
 * The user should be able to create/modify reports both through the Kibana UI or programmatically through APIs.
 * Ability to schedule/trigger reports periodically (a cron based schedule) or at a given frequency continuously or within certain time range.