New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Users do not get notified when an export ends #3139

Closed
rowasc opened this Issue Jul 6, 2018 · 2 comments

Comments

Projects
None yet
1 participant
@rowasc
Contributor

rowasc commented Jul 6, 2018

Describe the bug
Users do not get Notified when an export ends, they have to go to export history to see the status of their export. This always happens, it doesn't matter if the user stays on the export page or leaves the page.

Where was the bug observed
http://csvexportsforever.v3-qa.ush.zone/

To Reproduce
Steps to reproduce the behavior (Admin):

  1. Start a CSV export from the settings->export page
  2. The export will start.
  3. Wait (usually around 5-10) for the export to complete. Leave the export page.
  4. Check the export history page for status. If the job's status is data_export.exported_to_cdn or completed or failed, you should have received a notification.

Expected behavior
The user gets notified if an export fails.
The user gets notified if an export succeeds.

Is there a workaround? What is it.
Checking the history page for status updates.

Screenshots
No

Desktop Hardware Details (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone Hardware Details (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@rowasc rowasc changed the title from Users do not get Notified when an export ends to Users do not get notified when an export ends Jul 6, 2018

@rowasc

This comment has been minimized.

Contributor

rowasc commented Jul 6, 2018

@jrtricafort this looks like an annoying issue . :/ Eve found it while testing #3080, its not related to the fix but its obviously problematic. Can you prioritize?

@rowasc

This comment has been minimized.

Contributor

rowasc commented Sep 28, 2018

This is fixed, notifications work

@rowasc rowasc closed this Sep 28, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment