Better way to provide feedback on announcement posts

Question

I have started to use the new First Question and Answer queues and am finding issues with it.

The problem is finding out if the issue has already been reported.

The current way is to reply to the question announcing the new feature: Review queue workflows - Final release

But finding out is a problem. For example, I needed to see if not having a close button had been reported. Searching for "close" provides too many hits. In this case, because the question is so long.

I can think of two possible improvements

1. Provide a simple list of the headers of the answers (I suspect that this is too much work)
2. In this case it would have been easier if the announcement was one question (or even a blog post) and then reporting issues was a simple question Saying "Report issues on new queues here"

Answer 1

For this particular announcement post, I just posted a wiki answer consisting of a list of all^* the existing bug reports and feature requests.

Hopefully, this will make it easier for users to quickly find if their potential answer is a duplicate.

---

feature-request

As to the more general case,...

Maybe the company should automate this process by having answer templates for announcement posts where the template would contain some metadata placeholders for users to fill and that metadata would be used to automatically populate a list of reported bugs and feature requests. The template could be something like this:

<!-- tag: e.g., bug, feature-request -->
<!-- excerpt: Summarize your request or bug report in <100 characters  -->
<!-- status: Filled by staff -->

Or (probably better) infer the metadata directly from the answer's content. In that case, the template could be something like:

[tag:bug] | [tag:feature-request] <-- choose one

### Summarize your request or bug report in <100 characters

Then, the populating script would look in the markdown for the following:

• [tag:*] - to categorize the type of the answer/report
• the first heading - to be used as an excerpt
• [tag:status-*] - to categorize based on the status

As Journeyman Geek suggested, it would be great if there's a way for staff (actually, mods too) to pin that answer. Accepting the answer could be used as a workaround but accepted answers will be unpinned soon and it's currently only pinned when sorting by vote.

---

^* _{Sorry, if I missed any answers or messed up with the excerpt/link. The answer is Community wiki though, so anyone can improve it.}