fix(support): hide TransactionIssue + LimitRequest from ticket menu#586
Merged
TaprootFreak merged 1 commit intoMay 26, 2026
Conversation
Both types fail with HTTP 400 on submission because the app does not capture the API-required nested DTOs (transaction object / limitRequest object). Removing them from the type picker prevents users from filing tickets that can never succeed. Enum values and i18n keys are kept intact so re-enabling is a one-tuple revert once the proper form fields are implemented.
eec3a87
into
RealUnitCH:chore/post-580-followups
5 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Both
TransactionIssueandLimitRequestoptions in the in-app support ticket type picker silently fail with HTTP 400 on submit because the app never sends the API-required nested DTOs (transaction/limitRequest). The reproduction in the field isRealUnitApiException: limitRequest should not be empty (statusCode: 400)for LimitRequest; the TransactionIssue equivalent has not surfaced because realunit-app users typically file transaction issues via services.dfx.swiss instead.This PR hides both options from the picker until the proper forms are implemented. The enum values, i18n keys (
supportTransactionIssue,supportLimitRequest), icons, and the cubit's_getTicketNamemapping are intentionally left in place so re-enabling is a one-tuple revert per type once the structured input UI (dropdowns, transaction picker, document upload) lands.Why not implement the forms now
LimitRequestneeds three dropdowns (limit/investmentDate/fundOrigin), an optionalfundOriginTextfield mapped from message, a KYC ≥ 50 gate, and a mandatory document upload (PNG / JPEG / PDF). Requires a newfile_pickerdependency for PDF support.TransactionIssueneeds a transaction picker (list of the user's recent transactions viaGET /v1/transactions) plus a reason dropdown filtered to[FundsNotReceived, TransactionMissing, Other].Scope
lib/screens/support/subpages/support_create_ticket_page.dart— remove two tuples from theitems:array ofTagSelection<SupportIssueType>.Test plan
flutter analyze→No issues found! (ran in 4.7s)flutter test test/screens/support/→ 62 / 62 passedNeues Ticket erstellen, confirm onlyAllgemeines Anliegen,Fehlerbericht,KYC-Problemare selectable.