Closed
Bug 849312
Opened 11 years ago
Closed 11 years ago
[tracking] Backlog - Various sync issues
Categories
(Tracking Graveyard :: Metro Operations, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: MarcoM, Assigned: jimm)
References
()
Details
(Whiteboard: [tracking] feature=backlog)
New story recommended by Brian: Firefox Metro user I'd like my data to sync without any glitches. Referenced to: https://bugzilla.mozilla.org/show_bug.cgi?id=831615
Reporter | ||
Updated•11 years ago
|
Reporter | ||
Comment 1•11 years ago
|
||
Hi Asa, I've setup the basic for this story as Brian recommended. We just need the new user story and name for it.
Flags: needinfo?(asa)
Updated•11 years ago
|
Summary: Temp Story Name → Story - An glitchless sync experience
Updated•11 years ago
|
Summary: Story - An glitchless sync experience → Story - A glitchless sync experience
Comment 2•11 years ago
|
||
The story: As a Metro Firefox user, I experience a glitchless sync experience. This bug should be resolved when all user-facing dependencies are resolved.
Flags: needinfo?(asa)
Reporter | ||
Updated•11 years ago
|
Reporter | ||
Updated•11 years ago
|
Priority: P5 → P2
Reporter | ||
Updated•11 years ago
|
Priority: P2 → P3
![]() |
Assignee | |
Updated•11 years ago
|
Reporter | ||
Comment 3•11 years ago
|
||
Tracking backlog of related work to complete the 4 Sync Stories.
Reporter | ||
Updated•11 years ago
|
Whiteboard: feature=backlog → [tracking] feature=backlog
![]() |
Assignee | |
Updated•11 years ago
|
Blocks: metrov1backlog
![]() |
Assignee | |
Updated•11 years ago
|
Summary: [tracking] Backlog - A Glitchless Sync Experience → [tracking] Backlog - Various sync issues
![]() |
Assignee | |
Updated•11 years ago
|
Assignee: nobody → jmathies
Reporter | ||
Updated•11 years ago
|
![]() |
Assignee | |
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
OS: Windows 8 Metro → Windows 8.1
Updated•5 years ago
|
Product: Tracking → Tracking Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•