Icons instead tags

From MozillaWiki
Jump to: navigation, search
Please use "Edit with form" above to edit this page.


Icons or text tags instead of color tags
Stage Feature Inbox
Status `
Release target `
Health OK
Status note `


Product manager `
Directly Responsible Individual `
Lead engineer `
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead `
UX lead `
Product marketing lead `
Operations lead `
Additional members `

Open issues/risks


Stage 1: Definition

1. Feature overview

In my previous post I proposed to put colored numbers (representing the color tagged emails)after each folder from TB's left menu https://wiki.mozilla.org/Tagged_emails_name_and_count_after_the_foldernames This proposal would be an additional feature.

The problem: Color tags look simple but when you have multiple colors, than you don't remember the meaning for all of them. For example I remember that red tagged emails are important, and green ones financial emails, but I forgot what are the blue for.

The solution: Use icons instead of color tags OR use text tags. For icon tags see the attached image: Icon-tags2.jpg

2. Users & use cases

For example when I make my tax, I have to check my emails to see when money came in and when went out. For this I would make 2 icons (see image with pig icon) or simply I would create two text tag "money in" "money out" Than I would tag all the important emails accordingly and when I would need than I can find it better.

Another example: When I have to make an invoice for a client I have to check the exact sum in my proposal. I always spend a lot of time finding these emails. In this case a text tag would be more useful, like "proposal"

Another example and feature proposal: some email have different level of importance, and some of them has to be resolved in 2 days, we could have an icon or text tag with "date awareness" and could appear near the folder name, and you can see, that you have 3 important emails to resolve/answer today.

3. Dependencies


4. Requirements




Stage 2: Design

5. Functional specification


6. User experience design


Stage 3: Planning

7. Implementation plan


8. Reviews

Security review


Privacy review


Localization review




Quality Assurance review


Operations review


Stage 4: Development

9. Implementation


Stage 5: Release

10. Landing criteria


Feature details

Priority P3
Rank 999
Theme / Goal `
Roadmap Thunderbird
Secondary roadmap Add-ons
Feature list Thunderbird
Project `
Engineering team `

Team status notes

  status notes
Products ` `
Engineering ` `
Security ` `
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance ` `
User experience ` `
Product marketing ` `
Operations ` `