If I make an offer/request in Collaboration, I would like to be able to end it without bringing more attention to it by rising it to the top of latest by editing it.
2 Likes
This is what flags can be used for, i.e. the “Something else” section:
By doing so, a developer relations member will close your thread whenever they review the flag.
Alternatively, or additionally, you can send a DM to us, and we will be able to close to the thread for you too.
It kinda feels a bit annoying to ping top contributors when we should be able to do it ourselves.
8 Likes
I believe the main reason we are unable to is because of Discourse limitation, and not that they don’t want us to.
I believe in order for us to be able to close our own threads, we’d have to be able to close all threads. Unless there is a work-around, I don’t think we’ll get this ability anytime soon.
The Co-Foudner of Discourse himself pretty much said this’ll never be a thing in the software either.
Jeff Atwood codinghorror co-founder Jan '17
It is a bad idea. The potential for damage and cruelty is huge – just create a topic that says “user X sucks”, the delete it before any mods see it. Start a topic, then close it on a whim. So on, so forth.
There is also no plugin that I could find that would work as a work-around for this.
Like @cinderwtf points out, this is a limitation in Discourse’s features since there is no permission (as far as I know) that allows you to close just your own threads, and is also not desirable in some situations.
Also: you don’t just discuss for yourselves – the threads and posts you make are also useful to developers in the future who are struggling with the same questions/issues. Giving everyone the ability to close their own threads is inherently going to lead to more locked threads (since some people will do it just because they can, not because they should/shouldn’t), giving less opportunity to continue/improve the discussion.
It would be nice if we could toggle this per category so that we can let people close their own collaboration threads, but again, Discourse has no support for these kind of permissions. 
2 Likes
Considering Discourse is open source, I might see what I can do.
We would never allow users to close their own thread. This is super abusable, and the solution here is to not post threads that need to be locked in the first place (collaboration is an edge case).
What about the idea of being able to lock your own threads in specific categories as a permission?
That is not a solution at all. A solution is what @buildthomas gave.
There are valid cases for a thread to be closed by the OP. I.E if it gets derailed, a solution was made, or if the OP made a mistake when posting and didn’t realise it till others informed them.