The default bug view has changed. See this FAQ.

ProductDashboard page for a product only shows unresolved bugs in Priority section, but the "link" to that list shows all bugs

RESOLVED FIXED

Status

()

bugzilla.mozilla.org
Extensions: ProductDashboard
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: KWierso, Assigned: dkl)

Tracking

Production

Details

(Reporter)

Description

4 years ago
When I go to https://bugzilla.mozilla.org/page.cgi?id=productdashboard.html and choose the Add-on SDK product, I see in the Priority section that there are currently 7 bugs with a priority of "--". If I click the "link" link to view those seven bugs, I see a list of bugs that is cut off at 500 bugs, because the results are too large to show them all.

The same thing happens in the Severity table.

Bug Counts, Status, and Assignee work correctly, as far as I can tell.
(Reporter)

Updated

4 years ago
OS: Windows 8 → All
Hardware: x86_64 → All
(Assignee)

Comment 1

4 years ago
(In reply to Wes Kocher (:KWierso) from comment #0)
> When I go to https://bugzilla.mozilla.org/page.cgi?id=productdashboard.html
> and choose the Add-on SDK product, I see in the Priority section that there
> are currently 7 bugs with a priority of "--". If I click the "link" link to
> view those seven bugs, I see a list of bugs that is cut off at 500 bugs,
> because the results are too large to show them all.
> 
> The same thing happens in the Severity table.
> 
> Bug Counts, Status, and Assignee work correctly, as far as I can tell.

Thanks for the feedback. I see the issue and should have a fix committed soon for our next update.

dkl
Assignee: nobody → dkl
Status: NEW → ASSIGNED
(Assignee)

Comment 2

4 years ago
Will be in the next code push. Thanks.

Committing to: bzr+ssh://dlawrence%40mozilla.com@bzr.mozilla.org/bmo/4.2         
modified extensions/ProductDashboard/template/en/default/pages/productdashboard/summary.html.tmpl
Committed revision 8642.
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.