junlincc opened a new issue #13954:
URL: https://github.com/apache/superset/issues/13954


   
   Superset Roadmap item: 
https://github.com/apache-superset/superset-roadmap/issues/51 
   
   Request: Users, instead of going to dashboards, would like to receive data 
via email: PDF, 
   Screenshot, Link to dashboard or info “your data is available”. Based on 
alerts or Anomaly detection or data availability.
   
   Gaps in current Superset reporting:
   
   Setting up email / report schedules
   
   - [**Onboarding**]Add tooltips to the UI - even with the improved UI/UX it’s 
unclear what some of the fields in the setup mean
   - [**Timezone settings**] - currently only (default) option is UTC, ideally 
user can select their timezone (e.g select PST in a dropdown) and then setup 
time in PST
   
   Management of email schedules
   
   [**Configuration**] Admin can configure whether anyone can add anyone to 
email schedules or limited to above points.
   [**Subscription**]User can sign up for themselves and others to receive 
dashboard emails (setup dashboard to receive via email) 
   
   [**Schedule management**]Ability for a user (consumers) to see all their 
scheduled charts / dashboards (somewhat possible if they filter; maybe filter 
on their own schedules should be default in the UI)
   [**View subscription**]Ability for chart / dashboard owners to easily see 
who is subscribed to their dashboard
   When a change to subscription is made, the recipient & dashboard owner could 
be notified about the change.
   
   
   Security
   [**RBAC**] Security: All emails should be generated on the recipients 
permissions to access the data within the dashboard / chart. 
   Solution proposal: Check access to the section of dashboard which is being 
email; if user has access to all charts - include them in email; otherwise - 
just send them link to dashboard. → this addresses some of the perf. Concerns 
about each email being generated separately for permissions reason. 
   [**RBAC**] Dashboard owner can restrict “my dashboard is never emailable” → 
this addresses part of the Security issue.  
   
   Defining what to send - Tabs, Filters, Recipient
   [**Tabs**]Handling dashboards with multiple tabs: The email subscription 
should be per tab - user can select which tab to email or even select multiple 
tabs (?combination of nested tabs?) 
   [**Filters**] Being able to send dashboard tab with defined filters - not 
just default filters
   [**Recipient**] Ability to send email to “Dashboard owner” - in case owners 
change, recipients also change
   [**PDF**] Send in PDF not screenshot (PDF is standard, Looker, Tableau both 
send PDF)
   [**Text**] Ability to define short text/content to be included at the top of 
the email - currently it includes link to dashboard, users would like to 
include a short message, link to documentation, contact info, etc. 
   [**Mobile**] friendly views - needed for executive reporting
   Tooltips / visibility into values: Lot of charts are useful only with 
tooltips, since values are not displayed on the chart by default. If the chart 
has description it can be toggled on charts being sent via email. 
   
   Core functionality
   [**Triggering**]Trigger not based on specified time or alert, but based on 
“last week’s data landed”
   Meaning: instead of setting "send this dashboard every Monday 10am", set up 
as "as soon as the data for week lands (week ending sunday) send this 
dashboard" (it could be monday 10 am or 1pm)
   [**cleanup**] mechanism to prevent email schedules which are not longer used 
running
   
   Concerns:
   Performance, especially if each request is processed separately to apply 
user’s specific permissions. Can be executed on batch cluster (instead of 
dashboard cluster)
   Caching / data freshness - by default it uses data from cache - currently 
expected behavior but based on the time of the report data might be a day old 
(should be addressed longer term) 
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to