# הוסף הגדרה לבקרת העלאת נושא מיומנויות קטנות של "פוסטים פעילים"

**URL:** https://meta.discourse.org/t/add-setting-to-control-topic-bump-from-small-action-posts/365662
**Category:** Feature
**Tags:** small-actions
**Created:** [12 במאי,‏ 2025,‏ 1:57am UTC](https://meta.discourse.org/t/add-setting-to-control-topic-bump-from-small-action-posts/365662 "2025-05-12T01:57:36Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![per1234](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/per1234/32/569645_2.png) [@per1234](https://meta.discourse.org/u/per1234)
#### Post date: [12 במאי,‏ 2025,‏ 1:57am UTC](https://meta.discourse.org/t/add-setting-to-control-topic-bump-from-small-action-posts/365662/1 "2025-05-12T01:57:36Z")

</div>

### Feature description

When a staff action (e.g., “Close Topic”, “Pin Topic”) is performed on a topic, a special post (“small action post”) is automatically added to the topic.

Please add a setting that allows administrators to control whether small action posts will cause the topic to be bumped.

### Current behavior

The topic is bumped when a staff action causes the creation of a small action posts. This is often not helpful to the users.

For example, when a topic is closed due to the [“ **Auto-close topic after** ” category setting](https://meta.discourse.org/t/available-settings-within-the-category-edit-page/248435#:~:text=days%2C%20months%2C%20years%5D-,Auto%2Dclose,-topic%20after%3A), there is absolutely no benefit in surfacing that topic to users.

🙁 The user’s “Unread” topic list is polluted with topics which don’t have any activity of interest.

### Discourse version

`3146142c2ed2c880d53b2f8c136af9f46df99b59`

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [12 במאי,‏ 2025,‏ 5:55am UTC](https://meta.discourse.org/t/add-setting-to-control-topic-bump-from-small-action-posts/365662/2 "2025-05-12T05:55:21Z")

</div>

> [@per1234](#):
>
> The user’s “Unread” topic list is polluted with topics which don’t have any activity of interest.

I think there is a sneaky user preference that may help in this situation - ‘Consider topics unread when they are closed’. You can find it on your [https://meta.discourse.org/my/preferences/tracking](https://meta.discourse.org/my/preferences/tracking) page.

If you uncheck that it stops a topic close from being counted as ‘unread’.

* * *

**ETA:** Though there doesn’t appear to be an admin setting to choose the default in the same way as a lot of the other user preferences (the ones in `/admin/site_settings/category/user_preferences`). That might be a nice addition.

And just to clarify, when you say ‘bumped’ do you mean that they get the blue unread indicator and appear in `/unread`? I don’t think closed topics are bumped in the traditional way where they get put at the top of `/latest` (whether manually closed or by a timer).

Also, I think the auto-close timers use a ‘silent’ version of closing already where it suppresses the unread indicators, so hopefully those ones are not appearing in `/unread` lists. 🤞

---

<div class="post-metadata">

### Author: ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [12 במאי,‏ 2025,‏ 6:00am UTC](https://meta.discourse.org/t/add-setting-to-control-topic-bump-from-small-action-posts/365662/3 "2025-05-12T06:00:13Z")

</div>

זה היה שם יותר זמן? אני לא זוכר את ההגדרה הזו בכלל.

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [12 במאי,‏ 2025,‏ 6:04am UTC](https://meta.discourse.org/t/add-setting-to-control-topic-bump-from-small-action-posts/365662/4 "2025-05-12T06:04:45Z")

</div>

It was added 14 months ago  
[https://github.com/discourse/discourse/commit/f71e9aad60a63c5b98a6f9e20988874d01e97df4](https://github.com/discourse/discourse/commit/f71e9aad60a63c5b98a6f9e20988874d01e97df4)

---

<div class="post-metadata">

### Author: ![per1234](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/per1234/32/569645_2.png) [@per1234](https://meta.discourse.org/u/per1234)
#### Post date: [12 במאי,‏ 2025,‏ 10:13am UTC](https://meta.discourse.org/t/add-setting-to-control-topic-bump-from-small-action-posts/365662/5 "2025-05-12T10:13:10Z")

</div>

> [@JammyDodger](#):
>
> I think there is a sneaky user preference that may help in this situation - ‘Consider topics unread when they are closed’.

Thanks @JammyDodger. This is an effective workaround for the individual user, but I am requesting a solution the administrator can apply to the entire forum.

> [@JammyDodger](#):
>
> there doesn’t appear to be an admin setting to choose the default in the same way as a lot of the other user preferences (the ones in `/admin/site_settings/category/user_preferences`). That might be a nice addition.

It would, but that would only solve the problem for users who created an account after the time the default was changed, right?

> [@JammyDodger](#):
>
> when you say ‘bumped’ do you mean that they get the blue unread indicator and appear in `/unread`?

Correct.

> [@JammyDodger](#):
>
> I think the auto-close timers use a ‘silent’ version of closing already where it suppresses the unread indicators, so hopefully those ones are not appearing in `/unread` lists.

I have personally verified that they do appear in the `/unread` lists.

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [12 במאי,‏ 2025,‏ 10:38am UTC](https://meta.discourse.org/t/add-setting-to-control-topic-bump-from-small-action-posts/365662/6 "2025-05-12T10:38:02Z")

</div>

> [@per1234](#):
>
> It would, but that would only solve the problem for users who created an account after the time the default was changed, right?

When changing a default you can choose whether to apply it only going forward or to also update any existing ones:

 ![The image is a dialogue box asking if the user would like to apply a change to the default email digest frequency for historical purposes, affecting preferences for 13 existing users, with options to respond with "Yes" or "No". (Captioned by AI)](https://global.discourse-cdn.com/meta/original/4X/3/4/7/347f8bb2cd6b2e24dc8eb0c23a111c455f0dea06.jpeg)

If that preference admin setting was added then it should be possible to update all existing users too. 👍 (though for closed actions rather than the full suite of pinned, unlisted, split, etc)

> [@per1234](#):
>
> I have personally verified that they do appear in the `/unread` lists.

Which method are you using to auto-close them? There may be a version that’s not using the ‘silent’ option yet.

Sorry to focus on ‘closed’ ones, but they’re generally the worst offender when it comes to ‘noise’ like this. 🙂

---

<div class="post-metadata">

### Author: ![per1234](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/per1234/32/569645_2.png) [@per1234](https://meta.discourse.org/u/per1234)
#### Post date: [12 במאי,‏ 2025,‏ 11:34am UTC](https://meta.discourse.org/t/add-setting-to-control-topic-bump-from-small-action-posts/365662/7 "2025-05-12T11:34:42Z")

</div>

> [@JammyDodger](#):
>
> Which method are you using to auto-close them?

The [“ **Auto-close topic after:** ” category setting](https://meta.discourse.org/t/available-settings-within-the-category-edit-page/248435#:~:text=days%2C%20months%2C%20years%5D-,Auto%2Dclose,-topic%20after%3A) is set to 6 months.

The “ **Don’t close until the last post in the topic is at least this old.** ” category setting is enabled.

And to eliminate it from consideration as a possible factor, I’ll also mention that the “ **Number of open topics to automatically bump daily** ” category setting is set to `0`.

> [@JammyDodger](#):
>
> Sorry to focus on ‘closed’ ones, but they’re generally the worse offender when it comes to ‘noise’ like this.

It is fair. It is [complaints from users about the auto-close bumps](https://forum.arduino.cc/t/why-am-i-now-seeing-so-many-old-2024-posts-in-my-new-list/1379504) that motivated me to make this request.

Although less impactful due to occurring less frequently, it also doesn’t make sense to bump a topic when it is archived, and I also don’t think it makes sense to bump a topic just because it was unpinned. This is why I generalized my request instead of making it specifically about auto-close.

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [12 במאי,‏ 2025,‏ 12:12pm UTC](https://meta.discourse.org/t/add-setting-to-control-topic-bump-from-small-action-posts/365662/8 "2025-05-12T12:12:43Z")

</div>

> [@per1234](#):
>
> Although less impactful due to occurring less frequently, it also doesn’t make sense to bump a topic when it is archived, and I also don’t think it makes sense to bump a topic just because it was unpinned. This is why I generalized my request instead of making it specifically about auto-close.

I think these are very valid points and definitely worth a conversation to see if others also find these kind of things ‘non-events’ too. I know there’s been some discussion about not including these in the reply count for similar reasons.

> [@per1234](#):
>
> The [“ **Auto-close topic after:** ” category setting](https://meta.discourse.org/t/available-settings-within-the-category-edit-page/248435#:~:text=days%2C%20months%2C%20years%5D-,Auto%2Dclose,-topic%20after%3A) is set to 6 months.
> 
> The “ **Don’t close until the last post in the topic is at least this old.** ” category setting is enabled.

I did give this a test run earlier and my test user didn’t have them arrive in their `/unread`, but when I look at the `status_type` of the timers in [data explorer](https://meta.discourse.org/t/32566?silent=true) they’re getting a 1 (close) rather then an 8 (silent close) so there’s a chance I’m borking my test somehow. 🙂
