Skip to content

Release: develop -> main#1047

Open
github-actions[bot] wants to merge 4 commits intomainfrom
develop
Open

Release: develop -> main#1047
github-actions[bot] wants to merge 4 commits intomainfrom
develop

Conversation

@github-actions
Copy link
Copy Markdown

Automatic Release PR

This PR was automatically created after changes were pushed to develop.

Commits: 1 new commit(s)

Checklist

  • Review all changes
  • Verify CI passes
  • Approve and merge when ready for production

* feat: add support dashboard for internal issue management

- Add support dashboard with grouped issue list (awaiting reply, created, pending, on hold)
- Add issue detail screen with chat, file upload, update controls and info panels
- Add create issue screen with user search
- Add SUPPORT_DASHBOARD_ROLES constant shared between guard and navigation
- Add role-based access guard for Support, Compliance, Marketing and Admin
- Split error handling into blocking (load) and non-blocking (action) errors
- Support multiple file attachments per message
- Fix memory leak with Object URL cleanup

* chore: bump @dfx.swiss/react and react-components to 1.3.0-beta.267

* refactor: update support issue list endpoint path

* refactor: group support dashboard routes under support/dashboard

* refactor: remove marketing from department selection dropdowns

* refactor: use whitelist for department selection dropdowns
Add verifiedName field to the company onboarding header and add a
commercial register check comparing verifiedName with organizationName
(only shown when verifiedName is set).
…eback) (#1048)

* refactor: remove 'Login Kundenkonto' row from onboarding header

* fix: use fixed positioning for modal overlay

The modal was positioned absolute inside the scroll container, causing
it to appear at the top of the scroll area rather than the visible
viewport. Switch to fixed + overflow-y-auto so the modal always stays
in the viewport regardless of scroll position.

* feat: add createLimitRequest to compliance hook

* feat: extract LimitRequestFields for reuse

Move the Limit Request form fields (Name, Limit, Investment Date,
Fund Origin, Message, File) into a dedicated component so the same
UI can be reused in the compliance flow without duplication.

* feat: add Limit Request button in compliance onboarding

Compliance users can now create a Limit Request on behalf of a user
directly from the onboarding review (depositLimit row) and from the
user data panel. The modal reuses the shared LimitRequestFields
component so any future changes to the form apply to both the user
and compliance flows.

* feat: add stop transaction button with confirm dialog

* feat: add compliance chargeback flow with refund modal

Introduce a chargeback modal in the compliance transactions tab that
calls the new PUT /support/transaction/:id/chargeback endpoint to
release a refund. Extract reusable refund components (creditor fields
and data table) and refactor the bank-tx-return screen to use them.
Add STOPPED to the payment state labels and a getSupportUserInfo hook.

* chore: bump @dfx.swiss/react and react-components to 1.3.0-beta.268

* refactor: adapt frontend to consolidated refund endpoint

- Remove getSupportUserInfo and BankRefundData (no longer needed)
- Update chargeback URL from /chargeback to /refund
- Migrate bank-tx-return screen to use chargebackTransaction with nested creditorData

* refactor: remove unused Country import in refund creditor fields
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