Support
Support and Issue Reporting
Use this page to understand what to include when reporting a suspected forecast, journal template, account mapping, import, or Excel output issue.
How do I report a forecast issue?
The intended support path is the in-app issue reporting flow, backed by the API. Public email is not required for normal issue intake. Reports are designed to stay compact and do not intentionally store the full forecast model by default.
What to include in a useful report
- Issue type: journal template, account mapping, calculation, import, Excel output, or other.
- Where it happened: opening BS, transaction input, forecast result, checks, TB CSV import, or Excel export.
- Expected result and observed result.
- Relevant month, account name, transaction type, and template name if available.
Data boundary for reports
Avoid sending unnecessary confidential data. The feedback API accepts compact issue details and selected context fields for triage. If a review requires deeper evidence, create a minimized reproduction rather than sharing a full sensitive plan.
予測の不具合はどう報告しますか
仕訳ミス、勘定科目マッピング、計算結果、開始TB CSV取込、Excel出力に関する疑問は、アプリ内の報告導線から送る想定です。 メールアドレス公開ではなく、問い合わせ API で短い報告を受ける設計です。計算ミス 報告も、対象月と対象勘定を絞って送ると確認しやすくなります。
- 対象月、対象勘定、取引タイプ、テンプレート名を含めると確認しやすくなります。
- 想定値と実際の表示値を短く書くと、再現確認がしやすくなります。
- 機密情報や全モデルを送らず、必要最小限の内容にしてください。