1.0.1 Feedback: A Running List

Version 8

    This is a list of all bugs, issues, feature change requests, or documentation deficiencies reported in v1.0.1 of VizAlerts, for tracking purposes. I'll keep this up to date with newly reported issues, and add notes should they be fixed in a newer version. Alongside each is who found / suggested each issue / feature request:

     

    Items struck through have been fixed in v1.0.2. All other items will carry over to 1.0.2 Feedback: A Running List


    Bugs:

    1. CC and BCC addresses never have email sent to them for Advanced Alerts (toby e)
    2. Advanced alerts with email consolidation behave unpredictably due to unsorted CSV export (matt c)

     

    Functionality Changes:

    1. Do away with need to add a comment to Advanced Alerts (toby e)
    2. In a single email for an Advanced Alert fails, do not stop processing remaining email (toby e)
      1. (matt c): Initially I think we'll pre-validate the entire dataset, so that it is all-or-nothing
    3. Provide an intuitive way for end users to trigger a given VizAlerts manually for testing (toby e)
    4. Support additional formats for embedded content in Advanced Alerts (csv, pdf, png, etc) (toby e)

     

    Documentation Changes:

    1. Add instructions for "offline" Python package installation in install guide, for servers without Internet access (toby e)
    2. Add an "advanced setup" section to the install guide. (toby e)
    3. Expand the images in the documentation so they are more readable (toby e)