Closed Bug 1061592 Opened 10 years ago Closed 9 years ago

[User Story] As a helper I can select a question so that I can add a comment and get visual confirmation of submission.

Categories

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

All
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: RT, Assigned: espressive)

References

Details

User Story

As a helper I can select a question so that I can add a comment and get visual confirmation of submission.

Acceptance criteria:
* From the list of questions I can select a question to open it
* The helper can select the text area to enter a new comment (if X characters / Z words are entered / * I can only enter Z characters in a comment)
* The helper can submit a new comment, an indicator “Sending” is shown underneath the comment until the client receives confirmation from the server that the comment was submitted
* When the client receives confirmation from the server that the comment was submitted, the “Sending” indicator disappears and the time at which the comment was submitted get displayed instead.
* The “Receive new comment notifications” checkbox gets automatically checked so that the helper starts receiving notifications on all comments related to this discussion thread.

Attachments

(1 file)

      No description provided.
Adding implementation bugs as blockers.
Depends on: 1062407, 1068117
Depends on: 1089770
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
User Story: (updated)
* The “Receive new comment notifications” checkbox gets automatically checked so that the helper starts receiving notifications on all comments related to this discussion thread.

NOTE: From looking at the UX doc, it looks like the checkbox “Receive new...." will be checked be default.

This then means that after a helpee asked their first question, or a helper comments we need to set new_comment_notification to true for the relevant user.
The branch that contains the relevant work to add the, receive new comment notification field, and handle the update of the preference on the server and locally, lives here for now:

https://github.com/ossreleasefeed/buddyup/tree/bug1061592-add-new-comments-notification-checkbox
A note about the above. This sends a PATCH request to the server to update the preference but, at the moment the user object is missing the properties/fields for:

new_comment_notify
new_questions_notify

so, on the server side, the value is not being stored yet.
Those will be "user settings" which work similarly to the question metadata. The API for them isn't very good, but I couldn't convince DRF to do better. This will be landing soon, and I hope to be able to write some basic docs for these soon.
Depends on: 1109137
Assignee: nobody → schalk.neethling.bugs
Status: RESOLVED → REOPENED
Attachment #8542127 - Flags: review?(anthony)
Resolution: FIXED → ---
Just FYI, the PR is against the correct bug number. It relates to:
"* The “Receive new comment notifications” checkbox gets automatically checked so that the helper starts receiving notifications on all comments related to this discussion thread."

I know that this is not related to a sprint specifically but, it is work that has been done, would be a shame to loose it ;)
Comment on attachment 8542127 [details] [review]
https://github.com/mozilla/buddyup/pull/41

Although the code looks ok, it's not implementing something we want. The checkbox on a question is to disable notifications for this particular question. Here, you're disabling notifications for every question by changing the user global setting. This is bug 1061595.
Attachment #8542127 - Flags: review?(anthony) → review-
To disable notifications for a question, it's bug 1105767 and bug 1066386.

So I think we can close this again and work in one of those three bugs.
I agree with all of that, but I believe the question here is, is the code good to merge or not. It lays the groundwork, no need to throw it away?
Well it's not landable since it's not implementing the right feature. But it's not thrown away either, we can reuse parts of it for the correct features.
Ah yes, I see those individual bugs now but, a lot of the work I have been doing depends on work I did in https://github.com/mozilla/buddyup/pull/41 so, it would be great if we could get that merged in.

I know the checkbox does not function as it should, but changing that will be a lot easier than changing everything else I have done that followed on from that. You will for example see the update_preference function come to use again in https://github.com/mozilla/buddyup/pull/46

I really hope we can work this out, get this in and move forward.
Status: REOPENED → RESOLVED
Closed: 10 years ago9 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Flags: in-moztrap+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: