# Question topic and status?

**URL:** https://discuss.elastic.co/t/question-topic-and-status/245
**Category:** Meta Elastic
**Created:** [May 5, 2015, 7:48pm UTC](https://discuss.elastic.co/t/question-topic-and-status/245 "2015-05-05T19:48:33Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![wiibaa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wiibaa/32/44931_2.png) [@wiibaa](https://discuss.elastic.co/u/wiibaa)
#### Post date: [May 5, 2015, 7:48pm UTC](https://discuss.elastic.co/t/question-topic-and-status/245/1 "2015-05-05T19:48:33Z")

</div>

Hi,

do you plan to let topics be labeled as "question" with a possibility to flag them as answered and search between answered and unanswered ones easily.  
It was really repelling when visiting logstash-user google groups only occasionally.

Cheers

---

<div class="post-metadata">

### Author: ![tylerjl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylerjl/32/44965_2.png) [@tylerjl](https://discuss.elastic.co/u/tylerjl)
#### Post date: [May 5, 2015, 8:20pm UTC](https://discuss.elastic.co/t/question-topic-and-status/245/2 "2015-05-05T20:20:22Z")

</div>

I like this idea - especially considering that we're already seeing the majority of topics being posted are questions. Organizing via tags would help ease managing such a large subset of questions within disparate categories.

It would just be a matter of enabling the ability to tag topics. One concern would be that managing mis-labeled topics would become a burden, but I think crowdsourcing it - which is how Discourse works with user tagging anyway - and leaving the user level requirement in place would alleviate that problem.

@Leslie_Hawthorn, thoughts? /cc @kimchy

---

<div class="post-metadata">

### Author: ![Sam\_Saffron](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sam_saffron/32/44937_2.png) [@Sam\_Saffron](https://discuss.elastic.co/u/Sam_Saffron)
#### Post date: [May 6, 2015, 6:46am UTC](https://discuss.elastic.co/t/question-topic-and-status/245/3 "2015-05-06T06:46:13Z")

</div>

My recommendation here is to hold tight 3-4 weeks, this is planned:

> **[Solved Button Plugin](https://meta.discourse.org/t/solved-button-plugin/28129)**
>
> SEE: Customers often ask us for a “solved button” feature. This has been discussed a few times on meta. #7082 #26070 We are going to embark on building an official “Solved Button” I wanted to make sure it is very well specified prior. Prior Art...

In fact I started working on it, once its ready it will be available here.

---

<div class="post-metadata">

### Author: ![Leslie\_Hawthorn](https://avatars.discourse-cdn.com/v4/letter/l/7c8e57/32.png) [@Leslie\_Hawthorn](https://discuss.elastic.co/u/Leslie_Hawthorn)
#### Post date: [May 6, 2015, 5:25pm UTC](https://discuss.elastic.co/t/question-topic-and-status/245/4 "2015-05-06T17:25:19Z")

</div>

I like this solution - clean, visually appealing and will be familiar for folks using Discourse based forums elsewhere. ++ on sitting tight.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 1:48pm UTC](https://discuss.elastic.co/t/question-topic-and-status/245/5 "2017-07-06T13:48:00Z")

</div>


