Skip to content

Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
Minds Backend - Engine
Minds Backend - Engine
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Dependency List
    • Cycle Analytics
    • Insights
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 157
    • Issues 157
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 49
    • Merge Requests 49
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Packages
    • Packages
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Minds
  • Minds Backend - EngineMinds Backend - Engine
  • Issues
  • #142

Closed
Open
Opened 5 months ago by Jake Passi@JakePassi
  • Report abuse
  • New issue
Report abuse New issue

(bug): reporting boosts in boost queue causes accept/reject accidents

Summary

When reporting a boost, in the admin boost queue, and choosing "Another reason," it brings up a text box to type the other reason. As you type, it registers the keys and auto accepts/rejects pending boosts in the background while you're typing. (A key, E key, N key).

Ian Crossland created this task in Asana.

Additional commentary: https://app.asana.com/0/621013995005190/895504797715045

Steps to reproduce

(How one can reproduce the issue - this is very important)

Platform information

(Device, Android/iOS version, system stats, screen size)

App version

(App version and build number)

What is the current bug behavior?

(What actually happens)

What is the expected correct behavior?

(What you should see instead)

Relevant logs and/or screenshots

17

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Please solve the reCAPTCHA

We want to be sure it is you, please confirm you are not a robot.

Related issues
0

    • Jake Passi @JakePassi added P - Admin S - Triage (Questions) T - Bug labels 5 months ago

      added P - Admin S - Triage (Questions) T - Bug labels

    • Jake Passi @JakePassi moved from mobile-native#109 (closed) 5 months ago

      moved from mobile-native#109 (closed)

    • Mark Harding @markeharding added T - Bug (Triage) label and removed T - Bug label 5 months ago

      added T - Bug (Triage) label and removed T - Bug label

    • Ben Hayward @benhayward.ben added S - Triage (Review) label and removed S - Triage (Questions) label 3 months ago

      added S - Triage (Review) label and removed S - Triage (Questions) label

    • Ben Hayward
      Ben Hayward @benhayward.ben · 2 months ago
      Developer

      @IanCrossland is this still an issue?

    • Ben Hayward @benhayward.ben mentioned in issue front#91 (closed) 2 months ago

      mentioned in issue front#91 (closed)

    • Ben Hayward @benhayward.ben closed 29 minutes ago

      closed

    • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
    Please register or sign in to reply
    Assignee
    None
    Assign to
    None
    Epic
    None
    None
    Milestone
    None
    Assign milestone
    None
    Time tracking
    No estimate or time spent
    None
    Due date
    None
    3
    Labels
    P - Admin S - Triage (Review) T - Bug (Triage)
    Assign labels
    • View project labels
    None
    Weight
    None
    Confidentiality
    Not confidential
    Lock issue
    Unlocked
    3
    3 participants
    user avatar
    Ben Hayward
    user avatar
    Jake Passi
    user avatar
    Ian Crossland
    Reference: minds/engine#142