Monthly release for January 2022

Features

• Add support for checkbox questions by @dalmia in #258
• Endpoints for plio's, user's and org's settings by @deepansh96 in #282
• Adds support for copying plios from personal workspace to organisational workspace by @dalmia in #292

Enhancements

• Removes support for plio-analytics and BIGQUERY by @dalmia in #310
• Adds support for deleting items in bulks + deleting linked image if question is deleted by @dalmia in #296
• Increased expiry time of access token by @deepansh96 in #312
• Removes CMS_TOKEN by @Salonichoudhary07 in #305

Bug Fixes

• checks whether correct params for mobile have been passed during OTP request by @gurleen3 in #306
• Checks whether correct params have been passed during OTP verification by @Manyakalra3 in #304
• FIX: active workspace info was not being passed during SSO call by @deepansh96 in #222
• Sends raw total count of plios in paginated response by @dalmia in #266
• Enables super-admin of an org to view true user identity + code cleanups by @dalmia in #273
• Ensures that re-running Github Actions redeploys successfully by @deepansh96 in #288

New Contributors

• @Salonichoudhary07 made their first contribution in #305
• @Manyakalra3 made their first contribution in #304
• @gurleen3 made their first contribution in #306

Full Changelog: v0.4.1...v0.6

Monthly release for November

What's Changed

• Bug fix: we changed how we order the events while fetching them for a session to be ordered based on updated_at instead of their database id - by @deepansh96 in #255
• We are now using Django permissions to restrict access to plios instead of restricting access while the queryset for a Plio is created to be able to show the correct error message on the frontend (access denied instead of 404) - by @dalmia in #253
• Added support for Cypress integration in our frontend CI and made the respective changes in this repo to enable that - by @rathorevaibhav in #259
• Removed a welcome SMS that we were sending to users signing up through their phone as it was increasing our messaging cost by quite a lot - by @dalmia in #251

Full Changelog: v0.4...v0.4.1

Bi-weekly release for October

Enhancements

• #246 caches several API calls to dramatically improve the response time by @rathorevaibhav - the change in response time and the overall caching workflow can be seen below!

Change in response time:

Caching workflow:

Cache Invalidation workflow:

Monthly release for September

Features

• #243 embedding plios is supported now - the /play endpoint has been made public
• #240 we have changed the README accompanying the report for each plio from markdown to PDF and added a lot more explanation to clarify the way data is structured in Plio and the various terminologies that we use.

Enhancements

• #238 items corresponding to a plio are passed along with the PlioSerializer itself to prevent making additional API calls for fetching items

Weekly release for September

Features

• #234 support for deleting a plio and all associated objects

Bug Fixes

• #227 home page doesn't open for users logged in through SSO
• #230 calling is_superuser on request.user threw an error when a new user is created,

Monthly release for June

Features

• We support custom authentication for organizations to use their API KEY for bypassing Plio authentication for their viewer. Details here.
• We have set up monitoring and logging to trigger alarms when any of our services break. Details here.

Fixes

• We had recently created a data pipeline from RDS to BigQuery but the API for downloading report was still querying RDS

Enhancements

• Test coverage is now > 96%. 🥳

Weekly release for June

Features

• #187 we finally support adding images to questions 🥇
• #181 setting up automated testing finally! 😅
• #181 integration with codecov
• #183 #189 #194 #197 writing tests to get the coverage to almost 90% 🥳

Bug Fixes

• #125 via #183 The expiry time for OTP was not set to the correct timezone

Weekly release for June

Features

• #179 added new fields to the DB to support subjective questions

Enhancements

• #177 new field in the session table to track whether that session is the first for the given plio-user combination

Monthly release for May

Enhancements

• #165 New users now receive a welcome email from [email protected] instead of Aman's email ID 😛
• #171 #172 We tightened the security of Plio by restricting a lot of APIs that were earlier open for anyone who had their access token. This is a major security update.

Bug Fixes

• #174 Previously, sorting by the column names only sorted amongst the rows in the current page and not all the rows in the table.

Weekly release for May

Features

• #170 added a README to describe the contents of the data dump for each plio
• #166 we have switched the authentication provider connecting the frontend to plio-analytics from Auth0 to AWS cognito so that we remain within the AWS ecosystem and because Auth0 is almost 4 times more expensive.
• #164 an email is now triggered everytime the status of any user is changed from waitlist to approved through the REST API

Bugs

• #168 The retention array for a new user-plio session is now created on the backend instead of the frontend as creating an empty array on the frontend sometimes injected null values