v1.9.0 (released 2018-03-13)

Code diff: v1.8.0...v1.9.0

• Fix bug that was causing an exception when responding to a message
  from a user's inbox.

v1.8.0

v1.8.0 (released 2017-12-28)

Code diff: v1.7.0...v1.8.0

• Update RapidPro client library to 2.2 (fixing incompatibility
  with recent update to the RapidPro server).

• Change implementation of how_to_handle_sameday_responses to
  perform acceptably with nearly a million responses that we have
  in production. There will be a very long migration during the
  deploy, but after that, performance should be okay.

v1.7.0

v1.7.0 (released 2017-12-01)

Code diff: v1.6.1...v1.7.0

• Add an optional org setting, how_to_handle_sameday_responses, with
  two choices that control how to handle multiple responses to the
  same numeric question by the same contact in the same day.

  • use_last - charts display data as if the last response by
    a contact to the same question in the same day was
    the only response that day. This is the default value, and
    was always the behavior in previous releases.

  • sum - charts display data by summing all responses by the
    same contact to the same numeric question in the same day,
    as if they only answered once and their answer was that sum.
    This would be a change from previous behavior, and will require
    changing this in the org settings.
    (Non-numeric questions' responses continue the previous behavior,
    as described above in use_last.)

• When downloading responses, always include all responses in the CSV
  file. Previously, the responses downloaded were consistent with what
  the charts were showing, meaning if a contact responded multiple times
  to the same numeric question on the same day, only their last response
  was included.

v1.6.1

New infographic to guide the user through navigation between steps of making selections of data to track: Panels --> Cohorts --> Flows --> Fetch Runs

v1.6.0

• Contact sync updates with additional logging
• Question sync update
• UX adjustments:
  ** New navigation
  ** Clarified wording for Inbox Messages, Panels and Cohorts
  ** Updated wording to reflect RapidPro wording, "Poll" changed to "Flow"
  ** Fetch runs is now moved to the "Flow Runs" page and is it's own page

v1.5.4

• Google Analytics field editable for organization administrators and Google Analytics to website per org.
• Filter out polls that begin with "Single Message"
• Sync improvements
• Redis database fix: use different database for celery and cache
• Fix 500 on logged out access for Inbox Conversations

v1.5.3

• Rename Regions to Panels and Reporter Groups to Cohorts
• Smart Categories on single date numeric charts

v1.5.2

• Larger, sorted multi-select drop-downs
• Fixes for error emails from tasks
• Permissions fix for fetch runs front-end: Admins can now use this feature, in addition to super users.
• Fix redirect loop on change password
• Fixes for admins:
  • When someone is added to an org as an admin, make sure they're flagged as staff.
  • In the users list, add a column showing whether a user is staff or not.

v1.5.1

• API v2 Updates: Code now points to version 2 of the RapidPro API.

v1.5.0

• Many-to-many contact to group relation update in the back-end
• Allow admins to set super user status on the front end
• Web interface to manage fetch runs