The default bug view has changed. See this FAQ.

Let developer contact user/reply to user review

RESOLVED WONTFIX

Status

Marketplace
Consumer Pages
P5
enhancement
RESOLVED WONTFIX
3 years ago
a year ago

People

(Reporter: Raniere Silva, Unassigned)

Tracking

2014-Q2
Points:
---

Details

(Whiteboard: [ux][ui][design][marketplace-transition])

Attachments

(5 attachments, 1 obsolete attachment)

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release)
Build ID: 20140409030203

Steps to reproduce:

1. Go to "App Review" page of one of your apps.
2. Find the new review/comment with a bug report.
3. Click on "Report" link at the end of review/comment.
4. Select "Bug Report".


Actual results:

The "Report" link disappears.


Expected results:

Open a dialog window to write a message for reviewer requesting more information about the bug.
Can you be more specific about the STR?  I think you might be talking about the reviewer tools, but I can't tell.  I'm not sure what the "App Review" page is, and I don't see anything with bug report links.
I strongly suspect the reporter is talking about the front end 'Reviews' page (i.e. user reviews).  With that assumption in mind, I believe he/she is confusing the 'report' link - which flags it to the app review team - with a reply facility to ask the user for more details on the bug.
Component: Reviewer Tools → Consumer Pages
(Reporter)

Comment 3

3 years ago
Yes, I'm talking about the front end "Reviews" page/user reviews (e.g. https://marketplace.firefox.com/app/my-app-name/ratings).

Sorry about the confusing. I want a "reply facility to ask the user for more details on the bug".
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Contact Reviewer for help with bug report → Let developer contact user/reply to user review

Updated

3 years ago
Whiteboard: [mentor=bram][goodfirstbug][ux][ui][design]

Updated

3 years ago
Severity: normal → enhancement
Priority: -- → P5

Updated

3 years ago
Assignee: nobody → bram
Duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=968997
Duplicate of this bug: 968997

Comment 6

3 years ago
Can I fix this?

Comment 7

3 years ago
Abid: I think so! Let's just make sure.

Bram, are you working on this bug, or would you like to mentor Abid through the process?
Flags: needinfo?(bram)

Comment 8

3 years ago
Thanks for your interest! Yep. I’ll be the mentor of this bug.

The minimum viable actions that should happen are:
* User taps on “Report”
* User taps on “Misplaced bug report or support request”
* The modal window disappear. A new modal window appears to take its place. It will look similar to the “Report Abuse” interface
* Ideally, this window should not only give developers a text box to type a reply in, but also display the user review. By showing the original review, the developer can see the context and write a better reply.
* Make sure that the design fits within a 320x480 interface with a keyboard overlay underneath

You can start prototyping ideas on paper, and then uploading the scans here for review. Displaying user reply without crowding out the space designed for text box is an interesting problem to solve.

Sounds good?

Thanks for contributing!
Flags: needinfo?(bram)
(Assignee)

Updated

3 years ago
Mentor: bram@mozilla.com
Whiteboard: [mentor=bram][goodfirstbug][ux][ui][design] → [goodfirstbug][ux][ui][design]
dupe of bug 847947?
Flags: needinfo?(bram)
are there some news about this bug? it's very important to get more accurate details from users! thanks :)

Comment 11

3 years ago
(In reply to Andrew Williamson [:eviljeff] from comment #9)
> dupe of bug 847947?

Bug 847947 is a server operations bug. Is it possible that you’re posting the wrong bug here?


(In reply to niccolocantu94 from comment #10)
> are there some news about this bug? it's very important to get more accurate
> details from users! thanks :)

Abid Aboobaker is proposing to work on it, but we haven’t heard from him lately. Are you possibly interested in collaborating or helping out?
Flags: needinfo?(bram)
(In reply to Bram Pitoyo [:bram] from comment #11)
> (In reply to Andrew Williamson [:eviljeff] from comment #9)
> > dupe of bug 847947?
> 
> Bug 847947 is a server operations bug. Is it possible that you’re posting
> the wrong bug here?

sorry I meant bug 874947 - I suppose its not an exact dupe but is covering the same issue, that users are writing reviews rather than contacting the developer with bug reports.

Comment 13

3 years ago
@Bram - Is there any new development on this bug/feature or is it still on whiteboard practice stage? I am in need of a speedy fix for this. Would be willing to contribute if it's ok.

Comment 14

3 years ago
(In reply to karanjai.moz from comment #13)
> @Bram - Is there any new development on this bug/feature or is it still on
> whiteboard practice stage? I am in need of a speedy fix for this. Would be
> willing to contribute if it's ok.

If you’re willing to contribute, that’d be great! Please see comment #8 for a general guidance of how this bug should be handled. Post your prototypes here, and I will be available to give you feedback.

Comment 15

3 years ago
(In reply to Bram Pitoyo [:bram] from comment #14)
> (In reply to karanjai.moz from comment #13)
> > @Bram - Is there any new development on this bug/feature or is it still on
> > whiteboard practice stage? I am in need of a speedy fix for this. Would be
> > willing to contribute if it's ok.
> 
> If you’re willing to contribute, that’d be great! Please see comment #8 for
> a general guidance of how this bug should be handled. Post your prototypes
> here, and I will be available to give you feedback.

Yup I saw that before commenting :)
So to start you just need a wireframe and then I can start tinkering with the code, right? 
Have a few more doubts, do you want to continue the discussion here or there any irc or anyplace else I should visit

Comment 16

3 years ago
That’s right. It’s important that we get a wireframe that shows the flow our customers will go through to submit a report. When we know how it will work, then we can go ahead with the code implementation. And if you have any detailed question, ask me via email to avoid clogging the bug.
Mentor: bram@mozilla.com
Duplicate of this bug: 1044699

Comment 18

3 years ago
I just have the problem on my application https://marketplace.firefox.com/app/diaspora

A user is complaining about a missing feature which is implemented but I guess he didn't find it. I'd like to answer that the feature is not missing because that could confuse other people looking at reviews.

It looks like the marketplace doesn't allow to anwswer to reviews at the moment.

Updated

3 years ago
Duplicate of this bug: 1072282

Comment 20

3 years ago
Any updates? Really need this.

Comment 21

3 years ago
Hi, Bram - Are you only looking for a volunteer to do wire framing/user flow or will the person who picks this up also code the fix?

Comment 22

3 years ago
It looks like we've had a few people say they're interested in giving it a shot, but  no patches yet.

OK, everyone who's CC'd  on this: we've got a good sketch of the fix listed in comment 8, and a couple of people interested: show us what you've got so far, let's get this one over the line.

Comment 23

3 years ago
(In reply to Mike Hoye [:mhoye] from comment #22)
> It looks like we've had a few people say they're interested in giving it a
> shot, but  no patches yet.
> 
> OK, everyone who's CC'd  on this: we've got a good sketch of the fix listed
> in comment 8, and a couple of people interested: show us what you've got so
> far, let's get this one over the line.

Hi Mike and Brad - I've attached what I have by way of a wire frame for a UX solution. I noted my understanding of the ask and suggestions for slight alterations. The colors are only there to show contrasts/placement in the mobile environment. Also, I made notes related to mobile and web versions. My thought process is in HTML5 functionality so I would welcome any guidance on how Javascript might inhibit the proposal. I am hoping to work on this for my Ascend Project bug.

Comment 24

3 years ago
Created attachment 8502861 [details]
2014-10-10-dev_whiteboard.pdf

UX wire frame suggestions. I considered the size restrictions of this as a mobile solution, but it is not drawn to scale. These are some early ideas and do not contain any visual design elements. I look forward to feedback!

Comment 25

3 years ago
Hi Bram,
Would you mind uploading a screenshot of what the user currently sees when they are looking a review (or reviews)from within their account? Also, if there is a 'Report Abuse' workflow that I should see for comparison, that would be great, too. I uploaded a very early wire frame and suggestions that I will be improving over the weekend. 
Thanks in advance.
Flags: needinfo?(bram)

Comment 26

3 years ago
(In reply to Mike Hoye [:mhoye] from comment #22)
> It looks like we've had a few people say they're interested in giving it a
> shot, but  no patches yet.
> 
> OK, everyone who's CC'd  on this: we've got a good sketch of the fix listed
> in comment 8, and a couple of people interested: show us what you've got so
> far, let's get this one over the line.

Hi Mike - Greetings from Ascend Portland. I uploaded some early wire frame suggestions but didn't know if that would be considered a "patch" since it's not code. Should I upload the same thing today(Friday) or Monday as a patch or leave it as an image?

Comment 27

3 years ago
(In reply to Bram Pitoyo [:bram] from comment #8)
> Thanks for your interest! Yep. I’ll be the mentor of this bug.
> 
> The minimum viable actions that should happen are:
> * User taps on “Report”
> * User taps on “Misplaced bug report or support request”
> * The modal window disappear. A new modal window appears to take its place.
> It will look similar to the “Report Abuse” interface
> * Ideally, this window should not only give developers a text box to type a
> reply in, but also display the user review. By showing the original review,
> the developer can see the context and write a better reply.
> * Make sure that the design fits within a 320x480 interface with a keyboard
> overlay underneath
> 
> You can start prototyping ideas on paper, and then uploading the scans here
> for review. Displaying user reply without crowding out the space designed
> for text box is an interesting problem to solve.
> 
> Sounds good?
> 
> Thanks for contributing!

Hi Bram,
What do you think of the screen shots so far? https://bugzilla.mozilla.org/attachment.cgi?id=8502861
Candida
Flags: needinfo?(bram)

Updated

3 years ago
Duplicate of this bug: 1081032

Comment 29

3 years ago
Created attachment 8505263 [details]
Report Abuse - UI flow (current)

(In reply to dihaynes77 from comment #25)
> Would you mind uploading a screenshot of what the user currently sees when
> they are looking a review (or reviews)from within their account? Also, if
> there is a 'Report Abuse' workflow that I should see for comparison, that
> would be great, too.

Hi Candida,

Thanks for your contribution to this bug!

The current flow for reporting misplaced bug is attached here.

To clarify, there’s only one screen that needs to be designed. It’s the screen that shows up after the developer selects “Misplaced bug report”.

Your first pass at a solution looks great.

Moving forward, I would suggest drawing a lot of interface sketches on paper, scanning or taking pictures of them, and uploading them here.

Paper sketches may look like this:
https://encrypted.google.com/search?tbm=isch&q=ui+sketch+paper

I like how you’ve captioned parts of your mockups to explain what each part does (e.g. “x’s do not autopopulate”, “this should scroll”). You should continue doing this on paper.

Start sketching on what this interface could look like on a Firefox OS phone with the keyboards open. We’re looking at a 480x320 screen of about 3.5 inches diagonally. That’s the first step.

The second step is to take the same sketch and think of what the same interface could look like when scaled up for tablets and desktop.

After the second step is done and all the files have been uploaded here, we can have a look at them and decide on the best option to explore further.

The options worth exploring further will then be refined to a prototype that’s less sketchy. But we’ll save this for later!

Does this plan sound good to you? Am I unclear with my instructions above? Let me know!

Comment 30

3 years ago
(In reply to Bram Pitoyo [:bram] from comment #29)
> Created attachment 8505263 [details]
> Report Abuse - UI flow (current)
> 
> (In reply to dihaynes77 from comment #25)
> > Would you mind uploading a screenshot of what the user currently sees when
> > they are looking a review (or reviews)from within their account? Also, if
> > there is a 'Report Abuse' workflow that I should see for comparison, that
> > would be great, too.
> 
> Hi Candida,
> 
> Thanks for your contribution to this bug!
> 
> The current flow for reporting misplaced bug is attached here.
> 
> To clarify, there’s only one screen that needs to be designed. It’s the
> screen that shows up after the developer selects “Misplaced bug report”.
> 
> Your first pass at a solution looks great.
> 
> Moving forward, I would suggest drawing a lot of interface sketches on
> paper, scanning or taking pictures of them, and uploading them here.
> 
> Paper sketches may look like this:
> https://encrypted.google.com/search?tbm=isch&q=ui+sketch+paper
> 
> I like how you’ve captioned parts of your mockups to explain what each part
> does (e.g. “x’s do not autopopulate”, “this should scroll”). You should
> continue doing this on paper.
> 
> Start sketching on what this interface could look like on a Firefox OS phone
> with the keyboards open. We’re looking at a 480x320 screen of about 3.5
> inches diagonally. That’s the first step.
> 
> The second step is to take the same sketch and think of what the same
> interface could look like when scaled up for tablets and desktop.
> 
> After the second step is done and all the files have been uploaded here, we
> can have a look at them and decide on the best option to explore further.
> 
> The options worth exploring further will then be refined to a prototype
> that’s less sketchy. But we’ll save this for later!
> 
> Does this plan sound good to you? Am I unclear with my instructions above?
> Let me know!

Thanks for writing this! I appreciate the screen shots, too - they help me think about flow with the current UI. I can send some sketches later today(Wednesday).

Comment 31

3 years ago
Created attachment 8505676 [details]
Steps one and two - drawings

one of three. feel free to request more.

Comment 32

3 years ago
Created attachment 8505680 [details]
Step one A drawing

two of three

Comment 33

3 years ago
Created attachment 8505682 [details]
step one b drawing

two of three

Comment 34

3 years ago
Created attachment 8505683 [details]
step two c

three of 3
it's the same as "Steps one and two - drawings" obsoleted it bc my wording made things confusing.
Attachment #8505676 - Attachment is obsolete: true

Comment 35

3 years ago
(In reply to dihaynes77 from comment #30)
> (In reply to Bram Pitoyo [:bram] from comment #29)
> > Created attachment 8505263 [details]
> > Report Abuse - UI flow (current)
> > 
> > (In reply to dihaynes77 from comment #25)
> > > Would you mind uploading a screenshot of what the user currently sees when
> > > they are looking a review (or reviews)from within their account? Also, if
> > > there is a 'Report Abuse' workflow that I should see for comparison, that
> > > would be great, too.
> > 
> > Hi Candida,
> > 
> > Thanks for your contribution to this bug!
> > 
> > The current flow for reporting misplaced bug is attached here.
> > 
> > To clarify, there’s only one screen that needs to be designed. It’s the
> > screen that shows up after the developer selects “Misplaced bug report”.
> > 
> > Your first pass at a solution looks great.
> > 
> > Moving forward, I would suggest drawing a lot of interface sketches on
> > paper, scanning or taking pictures of them, and uploading them here.
> > 
> > Paper sketches may look like this:
> > https://encrypted.google.com/search?tbm=isch&q=ui+sketch+paper
> > 
> > I like how you’ve captioned parts of your mockups to explain what each part
> > does (e.g. “x’s do not autopopulate”, “this should scroll”). You should
> > continue doing this on paper.
> > 
> > Start sketching on what this interface could look like on a Firefox OS phone
> > with the keyboards open. We’re looking at a 480x320 screen of about 3.5
> > inches diagonally. That’s the first step.
> > 
> > The second step is to take the same sketch and think of what the same
> > interface could look like when scaled up for tablets and desktop.
> > 
> > After the second step is done and all the files have been uploaded here, we
> > can have a look at them and decide on the best option to explore further.
> > 
> > The options worth exploring further will then be refined to a prototype
> > that’s less sketchy. But we’ll save this for later!
> > 
> > Does this plan sound good to you? Am I unclear with my instructions above?
> > Let me know!
> 
> Thanks for writing this! I appreciate the screen shots, too - they help me
> think about flow with the current UI. I can send some sketches later
> today(Wednesday).

I uploaded some drawings yesterday but wasn't sure how to ping you on here. Also, how would you feel about sketches that are digital but just lines (rectangles etc.) and text. Having gone through both processes and losing a bug at a different Mozilla project after submitting drawings, I am definitely more comfortable submitting sketches that way. For me, it's faster and feels less restrictive.

Thanks, and let me know what you think of the ideas in the drawings or of you want more information.

Comment 36

3 years ago
I don’t think having two separate actions is necessary here. We only need the ability for developers to respond to a user’s comment. Mozilla doesn’t need to be notified of any bug.

So, having one button is fine. But the challenge here is, on the phone, screen real estate is limited. So how can we show *both* the user’s comment and the text box?

On tablet and desktop, laying the user comment and text box side by side looks good. Your solution here works out.

So the next step is to sketch the best way to utilise that small space on the phone. We’re working on a 320x480 screen of around 3.5" diagonal dimension, nearly half of it covered by the keyboard.

As far as submission format is concerned, use anything you feel comfortable submitting! If coming up with a lot of layout is faster to do with pen and paper, do that. If it’s faster on the computer, do that.

Your task and deliverable: explore enough layout variations on mobile, tablet and desktop sizes, and post them here. Feel free to combine them in one image if it makes your job easier.

I would suggest looking at:
* How we implement our review system today (go to any app on the Marketplace and select “Write a Review”)
* How the review system might look in the future (http://brampitoyo.github.io/marketplace-style-guides/app-details-review-write.html – it’s not yet final, but take it as an inspiration)

Comment 37

3 years ago
The inspiration is perfect and the deliverables are clear. Thank you! It's the last day of the Ascend Project so I will sketch and combine these this this weekend. Thanks!

(In reply to Bram Pitoyo [:bram] from comment #36)
> I don’t think having two separate actions is necessary here. We only need
> the ability for developers to respond to a user’s comment. Mozilla doesn’t
> need to be notified of any bug.
> 
> So, having one button is fine. But the challenge here is, on the phone,
> screen real estate is limited. So how can we show *both* the user’s comment
> and the text box?
> 
> On tablet and desktop, laying the user comment and text box side by side
> looks good. Your solution here works out.
> 
> So the next step is to sketch the best way to utilise that small space on
> the phone. We’re working on a 320x480 screen of around 3.5" diagonal
> dimension, nearly half of it covered by the keyboard.
> 
> As far as submission format is concerned, use anything you feel comfortable
> submitting! If coming up with a lot of layout is faster to do with pen and
> paper, do that. If it’s faster on the computer, do that.
> 
> Your task and deliverable: explore enough layout variations on mobile,
> tablet and desktop sizes, and post them here. Feel free to combine them in
> one image if it makes your job easier.
> 
> I would suggest looking at:
> * How we implement our review system today (go to any app on the Marketplace
> and select “Write a Review”)
> * How the review system might look in the future
> (http://brampitoyo.github.io/marketplace-style-guides/app-details-review-
> write.html – it’s not yet final, but take it as an inspiration)

I like this! I am at crunch time as the Ascend Project (open source training) ends today, but I can jot some things down this weekend.

Updated

2 years ago
Duplicate of this bug: 1103618
Any update on this?
Flags: needinfo?(dihaynes77)

Updated

2 years ago
Whiteboard: [goodfirstbug][ux][ui][design] → [good first bug][ux][ui][design]
Looks quite difficult bug for newbies, marking it as [good second bug] for now.
Whiteboard: [good first bug][ux][ui][design] → [good second bug][ux][ui][design]
note, it may be a good first/second UX design bug, but the actual implementation would be considerably more complicated.
Assignee: bram → nobody

Comment 42

2 years ago
Marking this for wontfix, we'll never get around to implementing this with our current resources.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX

Comment 43

2 years ago
Wow seriously? I didn't check the code of the app but to me it looks only like to add a text field "ownerAnswer" on the "comment" table. If you (or moco) is not going to fix it, at least let it open for volunteers to grab it.
That's the great thing about open source, "resources" can come any time to try and fix this.

Kevin: Unless you think this bug shouldn't be fixed, I suggest keeping it open.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---

Comment 45

2 years ago
Yeah, add the field to the model, write a migration, write a DRF view and serializer, tests, frontend design + UI for submitting and displaying it, frontend tests. And we might be rewriting the frontend soon. Grab it if you like.
Whiteboard: [good second bug][ux][ui][design] → [ux][ui][design]

Comment 46

2 years ago
Oh, and more notes. Permission checks from top to bottom that the user is the developer of the app.
Status: REOPENED → RESOLVED
Last Resolved: 2 years agoa year ago
Resolution: --- → WONTFIX
Whiteboard: [ux][ui][design] → [ux][ui][design][marketplace-transition]
Flags: needinfo?(dihaynes77)
You need to log in before you can comment on or make changes to this bug.