Closed
Bug 1040135
Opened 11 years ago
Closed 11 years ago
Include contents of "feedback" field in successful badge email
Categories
(Webmaker Graveyard :: Badges, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: doug, Assigned: erik)
References
Details
(Whiteboard: [badges] [design-debt] [email] [sep19])
At present, feedback is required whether or not the applicant was successful in their application for a badge.
If the badge is denied, the feedback from the reviewer is included in the generated email. However, if the badge is awarded, it is not.
I suggest that either:
(1) We include the positive feedback in the badge awarded email, or
(2) We remove the requirement to provide feedback if the badge is awarded
From a pedagogical and psychological perspective, I'd highly prefer (1). Going with (2) encourages people to just issue the badge - and it doesn't encourage suggestions r.e. how people can take their interests further.
Updated•11 years ago
|
Whiteboard: [badges] [aug8]
Updated•11 years ago
|
Whiteboard: [badges] [aug8] → [badges] [design-debt]
Comment 1•11 years ago
|
||
* Agreed. Let's go with (1) -- *always* include the feedback field
* Doug: a bunch of related badges email work is happening here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1046845
will need to co-ordinate how these various updates get made to those mails
Summary: Positive feedback should be included in successful badge email → Include contents of "feedback" field in successful badge email
Whiteboard: [badges] [design-debt] → [badges] [design-debt] [email] [sep5]
Comment 2•11 years ago
|
||
* This should be fixed soonish
Updated•11 years ago
|
Assignee: nobody → erik
Updated•11 years ago
|
Status: NEW → ASSIGNED
Comment 3•11 years ago
|
||
* status?
Flags: needinfo?(erik)
Whiteboard: [badges] [design-debt] [email] [sep5] → [badges] [design-debt] [email] [sep19]
| Assignee | ||
Updated•11 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•