Skip to content

fix: keep banned participants visible after reload, auto-rejoin on unban - #6521

Open
jmoehler wants to merge 3 commits into
mainfrom
jm-for-Phai2o/fix/4738-banned-participants-visibility
Open

fix: keep banned participants visible after reload, auto-rejoin on unban#6521
jmoehler wants to merge 3 commits into
mainfrom
jm-for-Phai2o/fix/4738-banned-participants-visibility

Conversation

@jmoehler

Copy link
Copy Markdown
Collaborator

As we didn't hear back from https://github.com/Phai2o on #6127, we took it in our own hands to finish the mr.

This is now the updated mr, containing the original changes puls updated snapshots and rebase on current main.

Phai2o and others added 3 commits May 18, 2026 11:12
Closes #4738.

- Participants.tsx: include banned participants in the list regardless of
  the connected/online filter, so a moderator can still reach the unban
  button after reloading the page (banned sessions are persisted as
  connected=false, which previously caused them to disappear).
- RejectionPage.tsx: when a user lands here with status="banned" and a
  boardId in the URL, silently probe the join endpoint every 30 seconds
  and surface a "Try to rejoin" button. On a successful re-admission the
  page dispatches permittedBoardAccess and the board mounts without a
  manual refresh.
  Probing goes through API.joinBoard directly instead of the joinBoard
  thunk so a still-banned response does not flip the redux status to
  pending and unmount the rejection page.
- i18n (en/de/fr): added bannedRetryHint, retry, retrying.
- styles: button group + retry button styling, dark mode respected.
@jmoehler jmoehler added Review Needed This pull request is ready for review Frontend At least some of this PR changes stuff in the frontend code labels Aug 18, 2026
@jmoehler

Copy link
Copy Markdown
Collaborator Author

@jmoehler: once this is approved, close #6127

@jmoehler jmoehler self-assigned this Aug 18, 2026
@github-actions

Copy link
Copy Markdown

The deployment to the dev cluster was successful. You can find the deployment here: https://6521.development.scrumlr.fra.ics.inovex.io
This deployment is only for testing purposes and will be deleted after 1 week.
To redeploy rerun the workflow.
DO NOT STORE IMPORTANT DATA ON THIS DEPLOYMENT

Deployed Images
  • ghcr.io/inovex/scrumlr.io/scrumlr-frontend:sha-f2ba78b

  • ghcr.io/inovex/scrumlr.io/scrumlr-server:sha-f2ba78b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bug (LOW) Frontend At least some of this PR changes stuff in the frontend code Review Needed This pull request is ready for review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants