Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 153 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

I went to the reqs tab from the meta homepage and I noticed that I was not able to paginate. Now, this really isn't that big of a deal, but there are two problems:

  1. It is ordered by votes, which means that you're likely to only see questions which were originally authored months, if not years ago. Personally, I view this as the real UI issue, but...
  2. It is counter-intuitive. One thing I think that SE has tried really hard to do is to make things as intuitive as possible, and this isn't.

Proposed solutions:

  • Have reqs simply link to the feature-request tab. I don't know how hard this would be, but it seems like it would be the most intuitive.
  • Order the page by recent activity and not by votes/question.
  • Have pagination on that page. I dislike this as I view it as inconsistent with the way that page normally works without adding benefiting the page much.
share|improve this question
up vote 2 down vote accepted

No need, just search for

[feature-request] -[status-completed] -[status-declined]

(add other not tags to taste, etc)

edit: good point, we should add the helpful text at the bottom offering the complete list.

share|improve this answer
    
There might be a point in putting this link at the bottom of the list, similar to the main page. Or simply doing this search (with sort=votes) instead of the current reqs tab. (The same is valid for "bugs"). – Paŭlo Ebermann Oct 4 '11 at 23:20
    
Here's a question for data.SE. How much of Jeff's rep. is based on "status-..." answers? – cwallenpoole Oct 5 '11 at 0:42

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .