Features

  • We added some tools to clean up unused data (VP-273).
  • We consolidated some parts of the Edit activity page to make it simpler to understand (VP-269).
  • We added some guidance text to the activity title and improved the language used for the activity requester (VP-247).
  • We added a pop-up confirmation that changes to an activity were successfully saved since there is now no Save button (VP-240).
  • We added some better signposting that the postcode can be searched (VP-238).
  • We removed contact information for event requesters (hosts) as it was not needed (VP-229).
  • We added certificates to profiles for Response Team volunteers (VP-226).
  • We changed the feedback widget to one that works with Jira (VP-157).
  • We add an export tool for settings not stored in CRM, including accounts and contact information visibility preferences (VP-155).
  • We added better handling of groups and organisations to reduce duplication (VP-130).
  • We added some additional security measures to prevent unauthorised access to data (VP-55).
  • We added a better widget to validate and format telephone numbers (VP-35).
  • We made activities editable by volunteers (VP-7).
  • Microsoft Graph tokens now get automatically refreshed (VP-156).

Bugs

  • We fixed an issue where changing the organisation type selection too quickly caused an error (VP-287).
  • We fixed an issue causing some users location not to be calculated properly (VP-279).
  • We fixed some errors in pulling Constituent data from CRM (VP-274).
  • Some Upcoming Activities were missing on users’ Home Page (VP-272).
  • We replaced hard coded Homepage quick links to the dynamic ones used on the Resources page (VP-270).
  • Contact details were not visible for activity leads (VP-265).
  • Activity roles were not appearing on the activity view page (VP-264).
  • The Host search box was too specific, causing it to miss results if you had missed a dot or hyphen (VP-263).
  • We fixed an issue which caused the Point of contact fields to become non-editable (VP-262).
  • The page was scrolling to the wrong location when entering activity information (VP-261).
  • A general error message was occurring when entering the portal (VP-260).
  • The word ‘null’ was appearing as a prefix and suffix on the activity host name (VP-255).
  • Passports were disappearing when cancelling an Edit (VP-254).
  • We fixed a data vulnerability when switching from a Selectable to a Non-Selectable activity requester (VP-252).
  • We fixed some activity location issues causing the map not to work (VP-250).
  • The list of Rotary Clubs was not populated (VP-249).
  • We fixed an issue with the Request SRT ID card function (VP-248).
  • We added caching of Google geocode results to reduce the number of API requests (VP-245).
  • We prevented contacts being shown for a Rotary Club selected as activity requester (VP-243).
  • We fixed condition which caused the application to hang when trying to access the activity edit page (VP-242).
  • We fixed an issue where the “back” button would roll back changes (VP-241).
  • We fixed a bug causing the activity requester section to become uneditable (VP-239).
  • We fixed an issue where some users could not see related people (VP-236).
  • Viewing an activity when it has been created by the source query but not pulled causes the date in CRM to be set to the current date (VP-234).
  • Labels and fields on the activity view page were poorly aligned (VP-230).
  • Using the Export/Import tool deleted CodeTables (VP-228).
  • We fixed an error that appeared when navigating to My Profile (VP-227).
  • We fixed an error that popup when a Search Query is cleared (VP-225).
  • We fixed a problem with the Directory/Activity Search (VP-224).
  • There was a SOAP Error when adding new Passport (VP-223).
  • We fixed a bug where an empty Activity Start Date caused an uninformative popup error (VP-221).
  • We fixed an issue with the visibility of volunteer addresses in the directory profile view page (VP-220).
  • We fixed a problem where constituents were constantly getting re-queued to be pulled from CRM (VP-218).
  • Phone Number types were not being imported (VP-207).
  • We fixed an error that occurred when searching with Directory (VP-204).
  • There was an issue with missing Lead and Assistant positions (VP-203).
  • We changed the intervals at which events and constituents are pulled from CRM (VP-201).
  • Nationalities were not getting pulled from CRM (VP-200).
  • Activity requester types were not getting pulled from CRM (VP-196).
  • Uploaded passport images were not getting deleted or rolled back when the cancel button was used (VP-193).
  • The passport upload did not save file extension (VP-191).
  • We fixed an issue with passports not syncing (VP-190).
  • The Activity Lead Required stats were incorrectly calculated (VP-183).
  • The first line of event briefings were formatted as <code/> (VP-179).
  • The activity location was not committing (VP-177).
  • We fixed an issue were the activity requester organisation or group was misbehaving (VP-176).
  • Some page events were prevented by validation checks (VP-175).
  • The relationship description was not getting added to comments (VP-174).
  • There was an error when editing biography (VP-172).
  • Biographies were missing from the profile view page in the directory (VP-171).
  • The management page for Resources tiles did not include a delete button (VP-170).
  • We tidied up the look of the profile view page in the directory (VP-169).
  • Several entities representing relationships are now specialised from a common generalisation (VP-163).
  • We fixed an issue causing the truncation of some datasets because the results of some instances of DataListLoad were not paged (VP-162).
  • We fixed a bug causing activities pulled from CRM by the scheduled event to be 1 hour different than when pulled by the user initiated action (VP-110).

Known issues

  • The country for phone numbers is not pulled from CRM causing an error to be generated by the phone number validation (VP-289).