Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark All Reports bug #2446

Closed
Ben-MyBB opened this issue Jul 12, 2016 · 1 comment
Closed

Mark All Reports bug #2446

Ben-MyBB opened this issue Jul 12, 2016 · 1 comment
Labels
b:1.8 Branch: 1.8.x p:low Priority: Low. Issue to resolve with low preference s:resolved Status: Resolved. Solution implemented or scheduled t:bug Type: Bug. An issue causing error / flaw / malfunction
Milestone

Comments

@Ben-MyBB
Copy link
Member

From modcp.php/action=reports page, if we check the box for mark all reports and then remove the check for one individual report the mark all button doesnt get uncheked..

Steps to reproduce:

  1. First report two or more posts
  2. Click on the unread report notice to go to the reports page.
  3. Now check the box for mark all. 
  4. then from the list of reported posts, remove check for any one report
  5. Now, the mark all check box remains checked and hitting the mark read button clears all reports, including the one unchecked in step 4.

Expected Behavior: when we remove check on any one individual report, the mark all button should get unchecked automatically

Original thread: Mark All Reports bug

@Ben-MyBB Ben-MyBB added t:bug Type: Bug. An issue causing error / flaw / malfunction s:confirmed Status: Confirmed. Retested and found the issue exists b:1.8 Branch: 1.8.x labels Jul 12, 2016
@Ben-MyBB Ben-MyBB added this to the 1.8.8 milestone Jul 12, 2016
@Destroy666x Destroy666x added the p:low Priority: Low. Issue to resolve with low preference label Jul 13, 2016
JordanMussi added a commit to JordanMussi/MyBB that referenced this issue Aug 14, 2016
@JordanMussi
Copy link
Contributor

Fixed in #2461. 😃

@effone effone added s:resolved Status: Resolved. Solution implemented or scheduled and removed s:confirmed Status: Confirmed. Retested and found the issue exists labels May 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
b:1.8 Branch: 1.8.x p:low Priority: Low. Issue to resolve with low preference s:resolved Status: Resolved. Solution implemented or scheduled t:bug Type: Bug. An issue causing error / flaw / malfunction
Projects
None yet
Development

No branches or pull requests

4 participants