Closed Bug 951779 Opened 11 years ago Closed 11 years ago

Don't list up to date articles on the localization dashboard.

Categories

(support.mozilla.org :: Localization, task, P1)

Tracking

(Not tracked)

RESOLVED FIXED
2014Q1

People

(Reporter: atopal, Assigned: rrosario)

References

Details

(Whiteboard: u=contributor c=wiki p=1 s=2013.25)

The most visited list on the localization dashboard should only show articles that need action. The list that links from the bottom of it should show all articles.
We are done for the year. Moving to next sprint. The way our readouts work, this isn't possible. So we need to figure out how to modify/redo them in some way. Sounds scary because the readout code is => 3pts for now
Whiteboard: u=contributor c=wiki p= s=2013.25 → u=contributor c=wiki p=3 s=2014.1
Component: Knowledge Base Software → Localization
unestimating and throwing back into current sprint after realizing how bad the current situation is. Let's try to fix quick today (I may have a fix hack already). If that doesn't work out, we'll roll back bug 943364.
Blocks: 939832
Whiteboard: u=contributor c=wiki p=3 s=2014.1 → u=contributor c=wiki p= s=2013.25
(In reply to Ricky Rosario [:rrosario, :r1cky] from comment #1) > The way our readouts work, this isn't possible. So we need to figure out how > to modify/redo them in some way. Sounds scary because the readout code is => > 3pts for now I overrode the render() method in this readout and was able to insert a hack so that it showed different rows depending on the value of the max_rows parameter which is only passed when on the main dashboard page. Then I was able to filter in python instead of SQL which made it much easier for me. I put up a branch on stage now for Kadir to verify the behavior. Then I will submit a PR.
This was about 1pt.
Whiteboard: u=contributor c=wiki p= s=2013.25 → u=contributor c=wiki p=1 s=2013.25
deployed to prod.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
oops, i did this
Assignee: nobody → rrosario
You need to log in before you can comment on or make changes to this bug.