Skip to content

Add Recent Activations widget and standardize myAvailability wording - #423

Merged
OSPFNeighbour merged 2 commits into
masterfrom
master-dev
Sep 1, 2026
Merged

Add Recent Activations widget and standardize myAvailability wording#423
OSPFNeighbour merged 2 commits into
masterfrom
master-dev

Conversation

@OSPFNeighbour

Copy link
Copy Markdown
Collaborator

This pull request introduces a new "Recent myAvailability Activation Requests" fieldset to the team creation page, allowing team creators to view recent activations for the assigned unit and quickly add responders from those activations directly into the team. It also includes supporting UI and logic, updates terminology for clarity, and adds associated styling.

New Feature: Recent Activations Fieldset

  • Added a dynamic fieldset to the team creation page (src/injectscripts/teams/create.js) that displays recent activations for the assigned HQ/unit. Users can expand activations to see categorized responder lists and add individuals to the team with one click. This feature is only enabled in production and integrates with external APIs for data.

Styling Enhancements

  • Introduced a new stylesheet (src/styles/teams.create.css) to provide visual structure and cues for the recent activations UI, including groupings, status colors, and interaction states.
  • Ensured the new stylesheet is loaded by requiring it in the content script (src/contentscripts/teams/create.js).

Terminology Updates

  • Updated references from "responders" to "responses" for clarity in the jobs view and team picker modal UIs (src/injectscripts/jobs/view.js). [1] [2]

Miscellaneous

  • Updated the global variable declaration in src/injectscripts/teams/create.js to include new dependencies.

OSPFNeighbour and others added 2 commits August 24, 2026 15:18
…ing (#421)

Lets a team creator load the last 5 myAvailability activations for the
assigned-to unit on the Beacon Team Create page, expand one to see who's
responded, and click a name straight into the team - no manual Refresh
by default, only fetches when a human asks, and refreshes automatically
on Assigned To changes after that first load.

Also standardises on "responses" over "responders" in the myAvailability
UI text in jobs/view.js and teams/create.js.
#422)

Previously the fieldset was hidden entirely outside production Beacon
since the myAvailability Lambdas have no train/dev data. Now it always
renders so the feature is discoverable, but shows a disabled Refresh
button and an explanatory message on train/dev instead of fetching.

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
@OSPFNeighbour
OSPFNeighbour merged commit 74f06f8 into master Sep 1, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant