Closed Bug 1098393 Opened 5 years ago Closed 5 years ago

[META] 2.2 Task Manager useability enhancements

Categories

(Firefox OS Graveyard :: Gaia::System, defect)

Other
Other
defect
Not set

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: wmathanaraj, Unassigned)

References

Details

(Keywords: feature)

User Story

With the Browser functionality integrated into the OS, the Task Manager becomes a critical method for navigation and saving content.  Task Manager Usability Enhancements revamps the UI of and adds new functionality (such as favoriting) to Task Manager.
No description provided.
User Story: (updated)
Keywords: feature
Summary: [User Story] Task Manager useability enhancements → [META] Task Manager useability enhancements
QA Contact: hcheng
What is the difference between this one and bug 1033971? I found they have similar titles and user story descriptions.
Flags: needinfo?(wmathanaraj)
that bug seems to be covering a lot more items than what we have defined for 2.2. So it made sense to have a meta for specifically the items we agreed for 2.2.
Flags: needinfo?(wmathanaraj)
Thanks for your explanation.

Could we put version number v2.2 in title to differentiate this story from bug 1033971 easily?
And, I found bug 1043406 isn't planning for 2.2. Do we need to remove it from depending list?
Flags: needinfo?(wmathanaraj)
No longer depends on: 1043406
Flags: needinfo?(wmathanaraj)
Summary: [META] Task Manager useability enhancements → [META] 2.2 Task Manager useability enhancements
still in 2.2 scope?
Flags: needinfo?(wmathanaraj)
(In reply to Hermes Cheng[:hermescheng] from comment #4)
> still in 2.2 scope?

I would think none of the dependencies here should block 2.2, maybe we should wontfix/invalid this meta and cherry-pick individual bugs if time allows
I'm closing as invalid. Since we re-defined the 2.2 scope, this bug isn't tracking anything useful (Bug 1040790 is not in scope for 2.2 and bug 967420 is its own meta bug.)
Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(wmathanaraj)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.