Closed
Bug 1061601
Opened 10 years ago
Closed 7 years ago
[user story] As a helper, I want mid air collisions to be handled so that I don't confuse the helpee with a comment not aligned with the last submitted comment.
Categories
(support.mozilla.org :: BuddyUp, defect, P4)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: RT, Unassigned)
References
Details
(Whiteboard: p=2 s=)
User Story
As a helper, I want mid air collisions to be handled so that I don't confuse the helpee with a comment not aligned with the last submitted comment. AC: * A notice is displayed when a message was posted between the contributor loading the question and submitting an answer * Contributor can dismiss it and post anyway * Contributor can throw his post away
No description provided.
Comment 1•10 years ago
|
||
For this user story, we need to send a request to the API to take a question when a helper starts typing something (I'm thinking focusing the input field). The server should clear the taken questions itself, no client side interaction. And for the lists, we'll probably have a flag to list taken/untaken/all questions. We'll also need the server to reject answers posted by someone else. And the error returned by the server should allow the client to distinguish with other types of errors.
Comment 2•10 years ago
|
||
I think that the right thing to do here would be to return "HTTP 409 Conflict". I think the UX also calls for the ability to overrule the lock and submit the message anyway. So there should be a way to tell the server to ignore locks after confirming with the user. Probably a parameter like { "ignore_lock": true }
Comment 3•10 years ago
|
||
That sounds good to me.
Comment 4•9 years ago
|
||
Romain, we have acceptance criteria for this, right?
Flags: needinfo?(rtestard)
Updated•9 years ago
|
Whiteboard: p=1
Reporter | ||
Comment 5•9 years ago
|
||
I thought we said (per comments on the AC doc) that this one was on the backlog (mid air collision) whilst we were addressing Bug 1061599 in phase 1?
Flags: needinfo?(rtestard)
Updated•9 years ago
|
User Story: (updated)
Priority: -- → P3
Updated•9 years ago
|
Whiteboard: p=1 → p=1 s=bu.2015.2
Updated•9 years ago
|
Summary: [User Story] As a helper, I can't comment on a discussion thread already being addressed by another helper so that I can't provide a comment not aligned with other helper comments. → [user story] As a helper, I want mid air collisions to be handled so that I don't confuse the helpee with a comment not aligned with the last submitted comment.
Updated•9 years ago
|
Whiteboard: p=1 s=bu.2015.2 → p=2 s=bu.2015.2
Comment 7•9 years ago
|
||
We are moving this out of this sprint and lowering its priority
Priority: P3 → P4
Whiteboard: p=2 s=bu.2015.2 → p=2 s=
Comment 8•7 years ago
|
||
Triaging old SUMO bugs. AFAIK buddy up is no longer supported and not under active development, so closing these out as won't fix.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•