Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Post History

62%
+3 −1
Q&A New Close reason needed

In this particular case, I would be inclined to disagree: the question has been answered before. It's just that the answer is actually given in a comment and a tag, not an answer post. "Can we get...

posted 4y ago by Canina‭

Answer
#1: Initial revision by user avatar Canina‭ · 2020-12-10T18:09:30Z (almost 4 years ago)
In this particular case, I would be inclined to disagree: the question **has** been answered before. It's just that the answer is actually given in a comment and a tag, not an answer post.

"Can we get Feature X?" where one of the people who do a lot of the work on the code responds with "This has been on my list for a while, but I haven't had the time to give it some thought so far." and puts the "status-planned" tag on the question is, IMO, pretty decisively answered: *that feature doesn't exist now, but we do plan to implement it.*

Maybe just change the close reason text from *this question has been answered before* to *this question has been **addressed** before*?