The discussion revolves around the issue of new tags updating topic currency in Discourse, which the user robbie.morrison finds counterintuitive. They note that adding a new tag to an old topic resets its age, making it appear fresh, which they believe is excessive for maintenance tasks. osioke suggests using the “Reset Bump Date” feature, but robbie.morrison reports that this did not work as expected despite using it. JammyDodger clarifies that the option must be clicked after saving, and robbie.morrison humorously concludes it’s a combination of feature, bug, and misunderstanding. Additionally, robbie.morrison mentions that inserting a table of contents via a div tag removes the visible wrench icon for accessing the reset feature, and JammyDodger explains that an alternative wrench icon is available at the bottom of the topic.
At present, adding a new tag to an old topic updates its currency. This seems a bit of an overreaction and it would be useful to be able to disable this functionality. Here is a screenshot example:
In this case, the tag scenarios was added and the topic age automatically resets to zero.
This seems somewhat counterintuitive to me because tagging is more like maintenance than content change? Indeed, as an admin, I quite often add tags to topics, even after some months or longer has passed. In which case, making the affected topics current again seems a bit excessive? TIA. R
I just undertook some tag maintenance to 22 topics and diligently used the reset bump date feature before saving in all cases. But that functionality does not seem to have taken and all 22 topics are now the freshest displayed. The site in question can be found here. I am the lead‑admin on the site and have only one account so I would have had full privileges.
Is this a feature, a bug, a regression, or a misunderstanding on my part? TIA. R
and then the little spanner icon on the right disappears. That is the icon I use to access the reset bump date feature. And I cannot do so with the TOC present. Is this a bug? Is there some other way of accessing the feature in question?