Closed Bug 1197080 Opened 9 years ago Closed 4 years ago

Allow to filter the revision dashboard by new pages

Categories

(developer.mozilla.org Graveyard :: Dashboards, enhancement)

All
Other
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: sebo, Unassigned)

Details

(Keywords: in-triage, Whiteboard: [specification][type:feature])

What problem would this feature solve?
======================================
It would allow to see which pages where created in a specific time span or by a specific user or generally all new articles.

John Whitlock indirectly expressed the need for this feature:
https://groups.google.com/d/msg/mozilla.dev.mdc/SnLYhbAi0Aw/0FYcEIMLBgAJ

Who has this problem?
=====================
All visitors to MDN

How do you know that the users identified above have this problem?
==================================================================
This suggestion is only based on use-cases.

How are the users identified above solving this problem now?
============================================================
Currently you need to check the list visually for any 'new' labels in the revision.

Do you have any suggestions for solving the problem? Please explain in detail.
==============================================================================
A simple checkbox labeled 'Only new pages' would solve that.
In case that people want to filter out new pages and just list changes to existing pages, a drop-down list labeled 'Entry type' (there's probably a better name) with the entries 'All' 'New', 'Existing' could be used.

Is there anything else we should know?
======================================
Component: General → Dashboards
MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.