Rapid Tower

• BRIDGE-3164: Add the originEventId to the StudyBurstInfo included in a timeline;
• BRIDGE-3140: Add studyTimeZone and adherenceThresholdPercentage to study object;
• BRIDGE-3142: Add session name/symbol to Timeline metadata;
• BRIDGE-3133: Add validation for string lengths that are too long for persistence;

Name from https://thestoryshack.com/tools/code-name-generator/

Clean Nighthawk

• BRIDGE-2605 - Participant versions API added
• BRIDGE-3121 - add 'test_user' data group to any participant enrolled in a study that is in 'design';
• BRIDGE-3130 - add a 'delay' period to a study burst configuration
• BRIDGE-3132 - add study burst information to the timeline, and to timeline metadata table
• BRIDGE-3140 - add study time zone and adherence threshold percentage to study, and relax criteria for study burst and custom event IDs
• timeline metadata recreation on a schedule create/update is now within the transaction persisting the schedule
• fix to study activity event query to retrieve the most recent version of each event (removes cases where there are duplicated event ID values in the returned values)
• fix activity event updates so that study burst information is carried over into the next event created

Name from https://thestoryshack.com/tools/code-name-generator/

Virtual Baron

• BRIDGE-3131: Fix server error where a very long user agent string causes persistence of RequestInfo to fail (failing the request);
• BRIDGE-2962: Add request parameter to the event activity map APIs so that they will return a 400 if the call fails to publish or delete an event;
• BRIDGE-3124: Fix record counts so they occur in the most recent activities map, and not in other activity event calls;
• BRIDGE-3123: Add information to events if they are derived from a study burst;
• BRIDGE-3120: Add request parameter to suppress updates of study burst events if their originating event is updated;
• BRIDGE-3113: Move study coordinator's API to trigger a participant roster export to the /v5/studies namespace;
• BRIDGE-3108: Elevate permission to force return of health code for apps that have health codes disabled so it only happens for super admins;
• BRIDGE-2803: Bridge should talk to Synapse development in development and staging/UAT;
• BridgeWorkerPlatform changes for https://sagebionetworks.jira.com/browse/BRIDGE-3092 Exporter 3.0 doesn't respect sharing settings
• fixing a couple of minor bugs not filed in JIRA (null pointer exceptions and one security check that was preventing correct behavior for organization administrators).

Name from https://thestoryshack.com/tools/code-name-generator/

See also

• https://github.com/Sage-Bionetworks/BridgeIntegrationTests/releases/tag/release-20211116
• https://github.com/Sage-Bionetworks/BridgeWorkerPlatform-infra/releases/tag/release-20211116
• https://github.com/Sage-Bionetworks/BridgeWorkerPlatform/releases/tag/release-20211116
• https://github.com/Sage-Bionetworks/BridgeWorkerIntegrationTests/releases/tag/release-20211116

Poised Gambit

• BRIDGE-3095: Add a study-specific note on a participant's enrollment
• BRIDGE-2962: Event APIs will now return 400 errors if requested, when an update will not occur
• BRIDGE-3112: Separate out participant roster export for study-scoped administrators
• https://sagebionetworks.jira.com/browse/BRIDGE-2122 - [SECURITY] Upgrade to TLSv1.2 (Infra, see https://github.com/Sage-Bionetworks/BridgeServer2-infra/releases/tag/release-20211103)

(Name generated from https://thestoryshack.com/tools/code-name-generator/)

Early Hammer

• BRIDGE-2610 - health data documentation (see design documentation).
• BRIDGE-2357/BRIDGE-3111 - fix is being introduced to make it possible to sign up anonymously with an external ID. Long-term this capability will be removed in favor of an authenticated API for enrolling users in studies not controlled by the caller;
• BRIDGE-3106/BRIDGE-3107 - email and phone number are added to the consent templates to aid in routing emails that are sent to the consent coordinator (this email is already a template and did not need to be converted);
• BRIDGE-3105 - added the field "symbol" to a schedule2 session in order to track an abbreviated representation of the session in UIs.

(Name generated from https://thestoryshack.com/tools/code-name-generator/)

Poor Cookie

• BRIDGE-3036: Enrollment APIs filter out studies that the caller does not have access to;
• BRIDGE-3101: Organization administrators no longer have access to participant accounts.

(Name generated from https://thestoryshack.com/tools/code-name-generator/)

Bully Knight

• BRIDGE-3092 Exporter 3 respects the sharing status flag on accounts and will not export their data when set to no sharing;
• BRIDGE-2950 Allows app configs to link to either assessments or shared assessments, not just assessments, similar to v2 schedules;
• BRIDGE-3053, BRIDGE-2865: Developers now can call any endpoint that manipulates participants, to read or edit accounts that are specifically marked as test accounts. Developers can only create test accounts and do not have any form of access to production accounts;
• BRIDGE-3073: Study bursts have been added to the v2 scheduler and to the study activity event system;
• BRIDGE-3094: Account deletion improvements. Caller can delete an account if it has never been used and is only enrolled in studies that the caller has access to;
• BRIDGE-3096: Data groups and roles are added to AccountSummary, allowing for some improvements when viewing lists of accounts or participants;
• BRIDGE-3097: Enrollment information has been added to the user session;
• BRIDGE-3099: Fix schedule access bug for admins in an org that sponsors a study, but doesn’t own the study’s schedule;
• Fixed synthetic events: some events that are dynamically calculated were not returning all fields that normal events were returning. This is now fixed.

(Name generated from https://thestoryshack.com/tools/code-name-generator/)

Deep Supernova

(Name generated from https://thestoryshack.com/tools/code-name-generator/)

• BRIDGE-3058: enrollment APIs no longer throw a cryptic database error if the study ID in the URL is not a valid study ID;
• BRIDGE-3065: physically deleting an app (a rare occurrence for us) no longer returns errors, and cleans up many of the new entities for Bridge v2, such as assessments, schedules, studies, etc.
• BRIDGE-3083: allow studies that are in design, legacy, completed, or withdrawn phases to be physically deleted, not just logically deleted. This will allow studies to be deleted such that their IDs do not pollute the ID namespace for studies;
• BRIDGE-3085: allow an account, if it has never been used to sign in to the Bridge server and it is enrolled in only one study, to be physically deleted. This will allow data entry errors to be corrected by deleting and re-entering the correct information.

Sleepy Olympus

(Name generated from https://thestoryshack.com/tools/code-name-generator/)

• https://sagebionetworks.jira.com/browse/BRIDGE-3067 - Exporter 3.0 initial implementation (BridgeServer). This is an additive change, but it uses the same upload APIs as Exporter 2.0. There is a risk that if the Exporter 3.0 code fails for an upload, this might also cause the upload validation for Exporter 2.0 to fail. Risks can be mitigated in that Exporter 3.0 is disabled by default and can be selectively enabled on a per-app basis.
• https://sagebionetworks.jira.com/browse/BRIDGE-3059 - Sessions triggered by multiple events. Administrative scheduling UIs will need to update, but there is migration code present so that clients using existing timelines do not break. Going forward they will need to update because the API for timelines is changing.

Ancient Mantis

(Name generated from https://thestoryshack.com/tools/code-name-generator/)

• BRIDGE-3044: Start using study-scoped custom events in the study-scoped event system;
• BRIDGE-3078: Fix performance problems when creating or updating v2 schedules;