Closed Bug 743712 Opened 13 years ago Closed 11 years ago

Display availability notification on profile page

Categories

(Mozilla Reps Graveyard :: reps.mozilla.org, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 987265

People

(Reporter: williamq, Unassigned)

References

Details

(Whiteboard: [kb=1076634] )

It would be good to add a field in the profile page where a Mozilla Reps can indicate that they plan to be unavailable for a specific period of time and that during their absence, people should contact another Rep.
Specs: * User can specify 1. Unavailability 2. Expected day to return 3. Replacement Rep * When activated send mentor an email * When expired send mentor an email * Do not automatically re-activate rep. * Update Mentor's dashboard to reflect user's inactivity.
Assignee: nobody → pierros
Status: NEW → ASSIGNED
Group: mozilla-reps-admins
Severity: normal → enhancement
Version: 0.2.5 - Sasak → 0.3 - Sarek
Whiteboard: mentor
Assignee: pierros → nobody
Summary: availability notification on profile page → Display availability notification on profile page
Version: 0.3 - Sarek → unspecified
Status: ASSIGNED → NEW
Severity: enhancement → normal
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: mentor → [good first bug][lang=python][lang=html]
Whiteboard: [good first bug][lang=python][lang=html] → [mentor=?][lang=python][lang=html]
Hi, I'm interested this. :williamq, could you please give me the details of this? Thanks!
Hi, I've setup remo on my local machine. Took the details from http://remo.readthedocs.org/en/latest/.
Siddardha, thank you for your interest! Unfortunately, after consulting with Pierros, the scope and functionality of this bug is yet to be determined by the Council. So, although this is a valid bug and a wanted feature for the ReMo portal, the exact implementation is yet to be determined. Updates about this bug will follow here. In the meantime, you can find some other bugs you might be interested here: https://wiki.mozilla.org/Webdev/GetInvolved/reps.mozilla.org
Status: NEW → UNCONFIRMED
Ever confirmed: false
Whiteboard: [mentor=?][lang=python][lang=html]
Whiteboard: [kb=1076634]
If the Rep does not manually opt-in with required information (i.e. they are auto-marked inactive after X months - see bug 951503), then we have to leave open the fields mentioned in comment 1.
Based on comment 1 and comment 6 and my own suggestions, I propose these specs: * User can specify 1. Unavailability 2. Expected day to return (optional, can only be set if unavailable = True) 3. Replacement Rep (optional, can only be set if unavailable = True) * Update Rep's profile to reflect user's inactivity * Update Mentor's dashboard to reflect user's inactivity * Do not automatically re-activate rep * Automatically mark Rep as unavailable when no report is filed after X months * When activated send mentor an email * When expired send mentor an email The first four specs feel like a minimal feature to me, and the automation and email notifications could be done in a release after that. Brian, could you review these specs and let me know if you agree with my suggestions or if you would implement/release this differently? Thanks!
Flags: needinfo?(bking)
Looks good to me. A couple of questions: 1. How will a Rep who has been automatically been deacvtivated activate again. Will, for example, the mentor have to do this automatically or will a new report do it? I'm a little concerned the new auto-reporting feature might trigger it prematurely. 2. What will deavtivated mode look like in the Reps profile? Designs welcome!
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(bking)
No longer depends on: 951503
We have some final specs for this developed by the group: https://remo.etherpad.mozilla.org/unavailable-rep-specs-2014-04-07 We also have a tracking bug for it. I'm going to close this one as a duplicate of the tracking bug and move focus there.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Product: Mozilla Reps → Mozilla Reps Graveyard
You need to log in before you can comment on or make changes to this bug.