Release Note, version 2.3.2

Release Note, version 2.3.2

We are here listing any and all relevant changes made to the app from last release post in November '22, which was then at v2.0.8.

Features

  • Top menu: new feedback form to notify us of bugs or things in the app that ought be improved on
  • Functionality and features in Evetro are hence divided into two tiers of user membership: the FREE tier, which is default for new users on the app; the BASIC tier, which grants the user all of Evetro's workshop features as well as expanded participant permissions. See our pricing page for more details.

Improvements

  • Various performance, security and code quality improvements
  • Top menu: Show menu item text when it is hovered over with the mouse
  • Sidebars: No cursor pointer when user profiles are not clickable
  • Create retro: No remove/"X" marker on your own user when you create a retro
  • Create&Edit Retro: Show cursor pointer when hovering over remove/"X" marker when you remove a user from a workshop
  • Timers: add extra sync events to improve relative clock accuracy
  • New re-implemented menu on the Mobile version

Fixes

  • Integrations: A tooltip was in the way of the permission checkmarks, so we took it out
  • Create/Edit Retro: Correct state flags for enabling a share link on a workshop
  • Edit Retro: Correct comparison callback for activities data
  • Create Retro -> Activities selection: Correct filtering function on past workshops in LastAction modal
  • ControlPanel -> Settings: Make user settings state persistant across client browser sessions
  • ControlPanel -> Settings: Remove user setting for consenting to Evetro's Terms Of Service. Non-assenting user will be expected to log off permanently going forward
  • Actions list: Correct stale component state
  • Adding team members to organization: Fixing a typo fixed this until now broken feature
  • Toggle buttons throughout the app should now be responsive and reflect the correct toggle state again
  • Fixed joining organizations by URL
  • Add a nullish check in the file handling component, which fixes a runtime error which would cause the app to crash