Firefox/Input/Standalone Feedback Button

From MozillaWiki
< Firefox‎ | Input
Revision as of 21:05, 14 April 2011 by Adesai (talk | contribs) (Created page with "{{draft}} {| class="fullwidth-table" |- | style="font-weight: bold; background: #DDD;" | Feature | style="font-weight: bold; background: #DDD;" | Status | style="font-weight: bo...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Draft-template-image.png THIS PAGE IS A WORKING DRAFT Pencil-emoji U270F-gray.png
The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly.
If you have any questions or ideas, please add them as a new topic on the discussion page.
Feature Status ETA Owner
Provide a standalone feedback button One or two sentence status report. YYYY-MM-DD aakashd

Summary

Succinct summary of what this feature is all about.

Team

Who's working on this?

  • Feature Manager: whoever is responsible for driving the feature to completion and updating the status on this page
  • Lead Developer:
  • Product Manager:
  • QA:
  • UX:
  • Security:
  • Etc.

Release Requirements

Complete checklist of items that need to be satisfied before we can call this feature "done".

Next Steps

Either the next set of tasks that need to happen to move this project along, or (ideally) the full list of project tasks/action items with things crossed off as they're finished. Including the name of who's responsible for each item can be useful.

Open Issues

Unanswered questions, things that need to be explored, decisions that still need to be made, etc. Again, including the name of who's responsible for each item can be useful.

Related Bugs & Dependencies

  • bug 649156 - Add the feedback button to the customize toolbar palette

Designs

Any and all mockups, design specs, tech specs, etc. Either inline or linked to.

Test Plans

Any and all test plans and strategies. Either inline or linked to.

Goals/Use Cases

The high level goals for the feature (which the release requirements checklist should fulfill). These are the guiding light and overall vision for the feature. Refer to this if there is confusion or are disputes about direction, designs, planning, etc.

Non-Goals

Things we are specifically not doing or building as part of this feature.

Other Documentation

Can include things like:

  • Competitive landscape
  • Research & references
  • Whatever else is useful to the project.

Legend (remove if you like)

  Healthy: feature is progressing as expected.
  Blocked: feature is currently blocked.
  At Risk: feature is at risk of missing its targeted release.
ETA Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.


Please remove this line and any non-relevant categories below. Add whatever other categories you feel are appropriate.

Retrieved from "https://wiki.allizom.org/index.php?title=Firefox/Input/Standalone_Feedback_Button&oldid=299284"