Closed Bug 831982 Opened 12 years ago Closed 12 years ago

Story - Touch friendly forms

Categories

(Tracking Graveyard :: Metro Operations, defect, P2)

Product:
Tracking Graveyard
Component:
Metro Operations
Platform:
x86_64
Windows 8.1
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: asa, Unassigned)

References

Details

Attachments

(1 file)

UC-140 Touch friendly forms
3.39 KB, text/html
Details
No description provided.
Priority: -- → P2
Whiteboard: c=Content_features u= p= → c=Content_features u=metro_firefox_user p=
Whiteboard: c=Content_features u=metro_firefox_user p= → c=Content_features u=metro_firefox_user p=20 (Asa to split up per form type)
OS: Windows 8 → Windows 8 Metro
Priority: P2 → P5
Whiteboard: c=Content_features u=metro_firefox_user p=20 (Asa to split up per form type) → feature=on_hold c=Content_features u=metro_firefox_user p=0 (Asa to split up per form type)
Depends on: 806456, 785425
Depends on: 801121
Whiteboard: feature=on_hold c=Content_features u=metro_firefox_user p=0 (Asa to split up per form type) → feature=story status=on_hold c=Content_features u=metro_firefox_user p=0 (Asa to split up per form type)
Summary: Touch friendly forms → Story – Touch friendly forms
Priority: P5 → P4
Whiteboard: feature=story status=on_hold c=Content_features u=metro_firefox_user p=0 (Asa to split up per form type) → feature=story status=on_hold c=Content_features u=metro_firefox_user p=0 status=on_hold
Depends on: 785764
No longer depends on: 801121
Blocks: metrov1onhold
No longer blocks: metrov1backlog
Depends on: 841141
Summary: Story – Touch friendly forms → Story - Touch friendly forms
Depends on: 833305
Component: General → Metro Operations
Product: Firefox for Metro → Tracking
Version: unspecified → ---
Depends on: 849699
Depends on: 849342
Depends on: 793635
No longer depends on: 849342
No longer depends on: 841141
Whiteboard: feature=story status=on_hold c=Content_features u=metro_firefox_user p=0 status=on_hold → feature=story status=on_hold c=Content_features u=metro_firefox_user p=20 status=on_hold
The writeup on this is incomplete. Seems as though it is shaping up to be a bug about form interaction bugs, independent of form scrolling which has its own story in bug 831980.
Flags: needinfo?(asa)
I'm also not sure if bug 806456 should block this, depending on its scope.
Yes, this has turned into a collection of forms touch interaction issues. Is that a problem?
Flags: needinfo?(asa)
(In reply to Asa Dotzler [:asa] from comment #5) > Yes, this has turned into a collection of forms touch interaction issues. Is > that a problem? Not at all, I'd like to work on it since it depends on bug 785425, which is the key bug in all of this. Can we take this out of onhold and add it to IT4?
Flags: needinfo?(mmucci)
No longer blocks: metrov1onhold
Depends on: skb
Alias: metro-forms
Hey Jim, going to confirm with Asa if the priority can be moved forward. In the meantime, would this be a Story with the possibility of being completed in 1 iteration or should the given work be split over multiple?
Flags: needinfo?(mmucci)
Depends on: 850422
More than one iteration, especially if we keep bug 806456 as a blocker. That's probably an iteration on its own. (I think that could be kicked out as a post v1 bug.)
Thanks Jim. Can you email with a list of how many works per iteration you believe is feasible and then I'll make the changes to reflect it.
Hi Jim, Asa has confirmed that Bug 806456 will be removed from this story and made into its own. We can move it to 'P2' for work this iteration as long as we break up the work across multiple iterations.
Priority: P4 → P2
No longer depends on: 806456
No longer depends on: 849699
Whiteboard: feature=story status=on_hold c=Content_features u=metro_firefox_user p=20 status=on_hold → [forms] feature=story status=on_hold c=Content_features u=metro_firefox_user p=20 status=on_hold
Whiteboard: [forms] feature=story status=on_hold c=Content_features u=metro_firefox_user p=20 status=on_hold → [forms] feature=story c=Content_features u=metro_firefox_user p=20
(In reply to Marco Mucci [:MarcoM] from comment #10) > Hi Jim, Asa has confirmed that Bug 806456 will be removed from this story > and made into its own. We can move it to 'P2' for work this iteration as > long as we break up the work across multiple iterations. bug 833305 & bug 850413 are the big projects here. Both could be broken out with their own point values. I'd really like to look at both of these in it5 so wee can nail down the rest of our keyboard / form interaction issues.
Hey Jim. Yes, we can break out Bug 833305 & Bug 850413 into their own stories with separate work dependencies and with individual point values. This will allow us to handle the development across multiple iterations while still making progress on closing them out as individual pieces.
Depends on: 854182
No longer depends on: skb
No longer depends on: 833305
Hey Jim, Bug 833305 & Bug 850413 have been removed as separate stories with their own point values. Do you need to change the point value on Bug 831982 or are you still good with 20?
Flags: needinfo?(jmathies)
Yes, this is lower with just the 3 minor bugs.
Flags: needinfo?(jmathies)
Whiteboard: [forms] feature=story c=Content_features u=metro_firefox_user p=20 → [forms] feature=story c=Content_features u=metro_firefox_user p=8
Depends on: 833305
Alias: metro-forms
No longer depends on: 854182
Depends on: skb
We should probably convert this into an epic.
No longer depends on: 833305
Lets just get rid of this. It's too generic anyway.
No longer blocks: 831565, metrov1backlog
Status: NEW → RESOLVED
Closed: 12 years ago
No longer depends on: 785425, skb, 785764, 793635, 850422
Resolution: --- → INVALID
Whiteboard: [forms] feature=story c=Content_features u=metro_firefox_user p=8
OS: Windows 8 Metro → Windows 8.1
Product: Tracking → Tracking Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: