These are the kind of posts you should avoid on old threads, they would qualify as bump posts:
I really need this.
This is still happening.
Bump, this would be really useful.
Why isn’t this solved yet? Support.
UPDATE: this is still open! (after only a few hours/days of the first post)
(quote here) This. I approve.
Thank you!
They do not add relevant information to the thread. They are annoying to read for other posters/readers and it bumps the thread back up to the top of Latest for no one’s benefit.
These are not bump posts:
I want to bring this bug report up again because it is still harming my work. I need to do X currently because of Y. This bug really needs to be addressed because Z.
Having this feature would really help my development work because of X.
Update: I added additional information to the first post, and there are still 2 open positions!
(The next one only if it is a collaboration thread that is about to be auto-locked, to signify it is still open:)
We still have some open positions available for X and Y!
Other situations where posting is fine even if the thread is old:
- Asking a question on a tutorial / community resource thread that hasn’t been previously asked + answered.
- Bumping an old feature request responding to an engineer mentioning that the feature would be released soon™, provided no one else has asked this recently.
- Bumping an old, solved bug report to let engineering know that it has resurfaced.
- Replying to a post in a discussion thread with significant new information/questions that contribute to that discussion. (Not just “How so? I disagree.” or “Yes, I approve of this” but actually explaining your full viewpoint and what you disagree/agree with).
Please be specifically careful about how you respond to old announcement threads. For discussion on old announcements, it may be better to find/create a different thread instead if you feel that your comment would not warrant bringing the whole thread back up again.