Closed Bug 669127 Opened 14 years ago Closed 11 years ago

[shipping] More info in sign-off column on l10n webdashboard

Categories

(Webtools Graveyard :: Elmo, defect, P2)

x86
Linux
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 696446

People

(Reporter: mad_maks, Unassigned)

Details

(Keywords: dogfood)

At this moment nl has 23 rows (products) on the l10n dashboard and when we change something in (for example) aurora it effects multiple products. We need to sign-off them all but you can not see on the dashboard witch one has a changeset good to sign-off. so you have so click all the accepted links. is it possible to add a status to the sign-off column (now; pending, accepted, no sign-off an accepted and pending) like accepted and possible sign-off?
My current idea is to show the date of the currently accepted push, for outreach triage. That isn't strictly the same thing, but might be a step forward. Not sure how bad it'd be to have the full computation as part of the dashboard, I'll have to think about that a bit more.
(In reply to comment #1) > My current idea is to show the date of the currently accepted push, this would be helpful allready
Keywords: dogfood
Priority: -- → P2
Summary: More info in sign-off column on l10n webdashboard → [shipping] More info in sign-off column on l10n webdashboard
Options as I see them: * remove earlier accepted status from sign-offs from a tree when going to another (ex: aurora -> beta - beta gets the accepted sign-off that existed in aurora, or none if there was none) * put a date on acceptance so we know which accepts are old (hacky but it's probably quicker to implement)
What is the status of this request?
ping
I think the "new" team pages resolved this. If there's stuff missing, it's probably good to file a new bug?
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
thanks for all your work
Status: RESOLVED → VERIFIED
Status: VERIFIED → RESOLVED
Closed: 13 years ago11 years ago
Resolution: FIXED → DUPLICATE
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.