Skip to content

[Due for payment 2026-03-13] [Domain Control] [Release 3.3] Report suspicious activity #79568

Closed

Description

@jmusial

Part of this project #76750

Implement reset domain:

Issue Owner

Current Issue Owner: @jmusial

Activity

  1. melvin-bot commented on Mar 4, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  2. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Mar 6, 2026
  3. changed the title [-][Domain Control] [Release 3.3] Report suspicious activity[/-] [+][Due for payment 2026-03-13] [Domain Control] [Release 3.3] Report suspicious activity[/+] on Mar 6, 2026
  4. melvin-bot commented on Mar 6, 2026

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  5. melvin-bot commented on Mar 6, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.31-12 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-03-13. 🎊

    For reference, here are some details about the assignees on this issue:

    • @jmusial does not require payment (Contractor)
    • @ZhenjaHorbach requires payment through NewDot Manual Requests
    • @situchan requires payment (Needs manual offer from BZ)
  6. melvin-bot commented on Mar 6, 2026

    @melvin-bot

    Triggered auto assignment to @jliexpensify (Awaiting Payment)

  7. rayane-d commented on Mar 6, 2026

    @rayane-d
    Contributor

    This is done 🎉

  8. ahmedGaber93 commented on Apr 26, 2026

    @ahmedGaber93
    Contributor

    Coming from #85528, the back button on the "Report Suspicious Activity" page doesn’t work because the backToRoute parameter is set to the same page.

    onBackButtonPress={() => Navigation.goBack(ROUTES.SETTINGS_LOCK_ACCOUNT)}

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions