# Topics moved into auto-close-able categories should autoclose
**URL:** https://meta.discourse.org/t/topics-moved-into-auto-close-able-categories-should-autoclose/58541
**Category:** Bug
**Created:** [March 7, 2017, 10:52am UTC](https://meta.discourse.org/t/topics-moved-into-auto-close-able-categories-should-autoclose/58541 "2017-03-07T10:52:27Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@iamntz](https://meta.discourse.org/u/iamntz)
#### Post date: [March 7, 2017, 10:52am UTC](https://meta.discourse.org/t/topics-moved-into-auto-close-able-categories-should-autoclose/58541/1 "2017-03-07T10:52:27Z")
Hey guys, I think I found a bug.
So, I have this category for job posting, where topics are automatically closed after 30 days since last post. This functionality works well.
_However_, some users posts this jobs in other categories and when an admin will move them in to the right category, I expect that they will close after 30 days (since, you know, is the category rule).
This should also work the other way around: if a topic is moved out of an auto-closeable category, it shouldn’t be closed anymore.
Make sense? 🙂
Thanks!
---
### Author:  [@tim.smith](https://meta.discourse.org/u/tim.smith)
#### Post date: [May 10, 2017, 2:31pm UTC](https://meta.discourse.org/t/topics-moved-into-auto-close-able-categories-should-autoclose/58541/2 "2017-05-10T14:31:21Z")
This is probably the same bug. My issue is that after turning on auto-close, only posts created _after_ setting the auto-close time will be auto-closed. Even if someone drags up an ancient post with a new reply, it doesn’t have the auto-close notice at the bottom of the page. I was hoping that there would be a nightly job or something to look for topics past the auto-close time that are still open, and then close them.
Is anyone aware of a workaround for my issue? Is there some command I can run to close topics that are older than the configured auto-close time? I’m not to keen on closing a year of posts manually.
---
### Author:  [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [May 10, 2017, 3:46pm UTC](https://meta.discourse.org/t/topics-moved-into-auto-close-able-categories-should-autoclose/58541/3 "2017-05-10T15:46:05Z")
I consider this a valid bug. @tgxworld do you have an idea how to fix this?
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [May 31, 2017, 8:44am UTC](https://meta.discourse.org/t/topics-moved-into-auto-close-able-categories-should-autoclose/58541/5 "2017-05-31T08:44:50Z")
> [@iamntz](#):
>
> However, some users posts this jobs in other categories and when an admin will move them in to the right category, I expect that they will close after 30 days (since, you know, is the category rule).
Thank you for reporting, this is fixed in
[https://github.com/discourse/discourse/commit/b0dd05fdc6b7b005ce8d37cd25d0be7a96fbe657](https://github.com/discourse/discourse/commit/b0dd05fdc6b7b005ce8d37cd25d0be7a96fbe657)
> [@iamntz](#):
>
> This should also work the other way around: if a topic is moved out of an auto-closeable category, it shouldn’t be closed anymore.
I don’t agree with this though. An admin may want to move a topic out of a category with auto close enabled without losing the auto close timer.
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [June 2, 2017, 3:39am UTC](https://meta.discourse.org/t/topics-moved-into-auto-close-able-categories-should-autoclose/58541/6 "2017-06-02T03:39:08Z")