Closed Bug 1085576 Opened 11 years ago Closed 11 years ago

"Mark As Solved" causes "Oh, no! It looks like an unexpected error occurred"

Categories

(support.mozilla.org :: General, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED
2014Q4

People

(Reporter: FredMcD, Assigned: rrosario)

Details

(Whiteboard: u=user c=questions p=1 s=2014.19)

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 Build ID: 20141011015303 Steps to reproduce: As the poster of a question, i received a message that there was a response to my question. I had pressed the "Mark As Solved" button. Actual results: I was redirected to the "Oh, no! It looks like an unexpected error occurred" page. Note: I had already flagged one of the responses as Solved. Expected results: Related: Bug 1018168 - Reply button on contributors e-mail go to wrong response when clicked
Component: Untriaged → General
Product: Firefox → support.mozilla.org
Version: 33 Branch → unspecified
Possibly this is an issue when you click the solve button from an email for a question already marked solved?
OS: Windows 7 → All
Priority: -- → P3
Hardware: x86_64 → All
Whiteboard: u=user c=questions p= s=2014.20
Target Milestone: --- → 2014Q4
> Actual results: > > Note: I had already flagged one of the responses as Solved.
It seems like marking a question as solved after it has already been solved is the problem. I see errors related to that in Sentry: https://errormill.mozilla.org/support/support/group/173065/ I think on the website we hide the mark as solved UI after there is a solution. Clearly we can't do this in emails. We should be more robust here.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Actually, I work on this today. Should be easyish.
Whiteboard: u=user c=questions p= s=2014.20 → u=user c=questions p=1 s=2014.19
While you are at it, can you do something about Bug 1018168 ? All you have to do is remove the Solved button from the e-mail. There are many, many that press the Solved by accident.
Deployed to prod.
Assignee: nobody → rrosario
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.