Closed
Bug 1250478
Opened 8 years ago
Closed 8 years ago
An app IARC Rating Certificate can’t be edited
Categories
(Marketplace Graveyard :: Developer Pages, defect, P1)
Marketplace Graveyard
Developer Pages
Tracking
(Not tracked)
VERIFIED
FIXED
2016-03-01
People
(Reporter: madalin.cotetiu, Assigned: mat)
References
Details
(Whiteboard: [triaged])
Steps to reproduce: 1. Open MP-dev Developer Hub https://marketplace-dev.allizom.org/developers/ 2. Submit a new app completing all the steps 3. Open The Content Ratings page of the new submitted app and try to edit the rating. Expected results: IARC questionnaire reappears for completion, a new content rating can be set. Actual results: The same IARC Rating reappears, the content rating can’t be changed. Notes/Issues Verified in FF44(Win7) Issue can be reproduced in mp-dev Screencast for this issue: http://screencast.com/t/uJX6Jk11
Updated•8 years ago
|
Assignee | ||
Comment 1•8 years ago
|
||
Can you re-test and screencast it from the beginning ? I want to see if the StoreRequestID we send to the questionnaire is the same for the 2 requests or not.
Flags: needinfo?(madalin.cotetiu)
Reporter | ||
Comment 2•8 years ago
|
||
Here is a screencast containing the full process: http://screencast.com/t/J525vV6d0bl2 Not sure about StoreRequestID, where should I see that? Is that the Certificate ID ?
Flags: needinfo?(madalin.cotetiu)
Assignee | ||
Comment 3•8 years ago
|
||
It's in the questionnaire URL, I checked and it's the same, which should not happen. I'll fix it.
Assignee: nobody → mpillard
Status: NEW → ASSIGNED
Comment 4•8 years ago
|
||
https://github.com/mozilla/zamboni/commit/22e2465e433f2ad6c0e3abc7a000808da8e40183
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Target Milestone: 2016-02-23 → 2016-03-01
Comment 5•8 years ago
|
||
Verified on FireFox47(Win7) IARC questionnaire reappears for completion, and users can submit a new form to get a new Certificate ID. Closing this bug.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•