Closed Bug 1061599 Opened 10 years ago Closed 9 years ago

[User Story] As a helper a discussion thread that is assigned to me gets automatically unassigned after 10 minutes of inactivity so that other helpers can get notified and comment on it

Categories

(support.mozilla.org :: BuddyUp, defect)

Product:
support.mozilla.org
Component:
BuddyUp
Platform:
All
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: RT, Assigned: rik)

References

Details

(Whiteboard: s=bu.2015.1 p=2)

User Story

As a helper a discussion thread that is assigned to me gets automatically unassigned after 10 minutes of inactivity so that other helpers can get notified and comment on it

Acceptance criteria:
* If a helper picks a question from the list of “New” questions that is not assigned yet, this question gets assigned to him for a duration of 10 minutes after the last activity on the question. Activity on the question is defined as “A helpee or a helper comments on the question” 
* If a helper picks a question from the list of “New” questions that is already assigned to another helper, the helper gets displayed a new screen notifying him that another helper is addressing the question. The helper can acknowledge the message to get back to the list of questions that gets re-synced automatically.

Attachments

(1 file)

https://github.com/mozilla/buddyup/pull/56
42 bytes, text/x-github-pull-request
rehandalal+mozilla
: review+
Details | Review 
      No description provided.
Summary: [User Story] As a helper I discussion thread that is assigned to me gets automatically unassigned after 10 minutes of inactivity so that other helpers can get notified and comment on it → [User Story] As a helper a discussion thread that is assigned to me gets automatically unassigned after 10 minutes of inactivity so that other helpers can get notified and comment on it
User Story: (updated)
Blocks: 1109642
Whiteboard: s=bu.2014.4
Mike: I don't remember what we decided for this. Do we have to do anything on the client for this? Like call an API to assign a question to a helper?
Flags: needinfo?(mcooper)
Whiteboard: s=bu.2014.4 → s=bu.2015.1
You'll have to call an API to take a question. The question will automatically be unassigned after 10 minutes by the server. The API is `/api/2/question/<id>/take`. The desktop site is actually already doing this as well. To avoid showing these to users, you'll have to add a filter to your API call to list questions, `?taken_by=null` (though I just checked and this doesn't seem to work. I'll have to fix that).
Flags: needinfo?(mcooper)
Assignee: nobody → anthony
Status: NEW → ASSIGNED
Depends on: 1119886
Whiteboard: s=bu.2015.1 → s=bu.2015.1 p=2
Depends on: 1120480
Joni: The wording in the UX spec is currently:
# Previously Answered
Another helper has answered this question, please choose another.

But the purpose of this feature is to prevent helpers to answer at the same time (we assign the question for 10 minutes to a helper as soon as she starts typing). So the wording should reflect that (something in the spirit of "Someone else is currently answering, come back later or pick another question")
Flags: needinfo?(jsavage)
Depends on: 1120978
I need to modify the code once bug 1120480 lands. For now, I'm displaying the overlay whenever the question is taken (even by you).

Questions that are taken will also still display in the list because of bug 1119886.
Attachment #8548235 - Flags: feedback?(rdalal)
Updated to only mark a question as taken if it's not by you and respect the taken_until field. We still need bug 1120978 to fix the timezone.
Attachment #8548235 - Flags: feedback?(rdalal) → review?(rdalal)
https://github.com/mozilla/buddyup/commit/9757911c3576ca52a1edc4a1f06fc9941a067a1f
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Sorry, @rik, I was out last week. For the wording (if it's not too late), how about:


"#Incoming Answer

Someone's already answering this question. Please check again in 10 minutes or answer another one."

* If we don't want to set the expectation that the thread will be unlocked in 10 minutes, we can say:

"Someone's already answering this question. Please check again later or answer another one."
Flags: needinfo?(jsavage)
Thanks Joni. We'll open a bug to modify once we have the final wording document.
Depends on: 1127409
Depends on: 1128468
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: