# 지우기 조언을 해도 실제로 지워지지 않아요

**URL:** https://meta.discourse.org/t/clearing-advice-doesnt-actually-clear-it/398754
**Category:** UX
**Tags:** fixed
**Created:** [3월 18, 2026, 7:34오후 UTC](https://meta.discourse.org/t/clearing-advice-doesnt-actually-clear-it/398754 "2026-03-18T19:34:57Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![ted](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ted/32/283882_2.png) [@ted](https://meta.discourse.org/u/ted)
#### Post date: [4월 6, 2026, 1:42오전 UTC](https://meta.discourse.org/t/clearing-advice-doesnt-actually-clear-it/398754/4 "2026-04-06T01:42:10Z")

</div>

합치면 특정 문제 검사에 대한 알림을 무시할 수 있게 해주는 PR을 열었습니다. 또한 모든 검사의 상태를 확인하고 무시 설정을 취소할 수 있는 대시보드 탭도 함께 추가되었습니다.

> <https://github.com/discourse/discourse/pull/39103>
>
> \## Background
> 
> Currently you can "dismiss" problem checks on the dashboard, bu…t if the problem persists it will show up again on the next reload, which is confusing.
> 
> There was previously some discussion about adding a feature to "snooze" problem checks, but I think even with that it remains a bit too opaque. You'd need to spelunk around in the console to try and figure out what is going on.
> 
> \## What is this change?
> 
> This PR does a couple of things:
> 
> \### 1. Replace Dismiss with Ignore
> 
> Hitting ignore will prevent the problem check from creating new admin notices until it has been unignored from the new problem checks page.
> 
> \*\*Screenshot\*\*
> 
> \<img width="395" height="61" alt="Screenshot 2026-04-05 at 4 37 39 PM" src="https://github.com/user-attachments/assets/4816fd04-046b-441e-9471-c160dd3f82b9" /\>
> 
> \### 2. Add a new problem check page
> 
> This page provides a list of problem checks with information on whether they are passing or failing, and when they were last run. You can also ignore or unignore (watch) problem checks from here.
> 
> \*\*Screenshot\*\*
> 
> \<img width="600" height="200" alt="Screenshot 2026-04-05 at 4 26 37 PM" src="https://github.com/user-attachments/assets/d8cb2b6a-3f56-409c-97f0-312cb1545654" /\>
> 
> \### 3. Remove the problem check timestamp from the dashboard
> 
> This timestamp made sense under the previous model, where all checks were run at once and the results cached. With the new model, there's a mix of on-demand and scheduled checks, and having a single timestamp is misleading at best. In practice it's always going to be just the timestamp when you last loaded the dashboard.
> 
> \*\*Before\*\*
> 
> \<img width="240" height="100" alt="Screenshot 2026-04-05 at 4 30 21 PM" src="https://github.com/user-attachments/assets/1846e024-0042-476e-8b5d-41b6745af75f" /\>
> 
> \*\*After\*\*
> 
> \<img width="210" height="95" alt="Screenshot 2026-04-05 at 4 29 19 PM" src="https://github.com/user-attachments/assets/a39c87c1-c1e3-4621-8219-e3903ba2ada4" /\>

이 PR은 Discourse 스태프(예: @kris.kotlarek)의 검토 및 합치를 받아야 합니다. 🙂

---

_[View the full topic](https://meta.discourse.org/t/clearing-advice-doesnt-actually-clear-it/398754)._