Closed Bug 1040800 Opened 6 years ago Closed 6 years ago
Breakdown: FHR & telemetry unification, client side work, phase 1
No description provided.
Summary: Breakdown: FHR & telemetry unification, client side work → Breakdown: FHR & telemetry unification, client side work, phase 1
I'm planning to get to this in the next iteration - can we get it in there or should i just pick it up when i can get to it?
Depends on what you want to commit to for 34.3. If this is more important than the other work you would commit to, then we should add it now.
I have to take a look at the next iterations list today if there's anything critical, but i should get started on this soon so thie work items aren't delayed too much.
Assignee: nobody → georg.fritzsche
Iteration: --- → 34.3
Added to IT 34.3
Status: NEW → ASSIGNED
QA Whiteboard: [qa-]
We want to have the stable id in telemetry soon, so that is happening first. Phase 1 of unifying FHR & telemetry will be mostly limited to that and potential related issues.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Project plan and context: https://docs.google.com/document/d/1IGpzsYGi_sq3YFQDAPyKOkU_BKvXAC95fZYA2i4ceVs/edit?usp=sharing
Product: Firefox Health Report → Firefox Health Report Graveyard
You need to log in before you can comment on or make changes to this bug.