Closed
Bug 967683
Opened 12 years ago
Closed 12 years ago
Completing submission of an existing app doesn't check for content rating setup before updating the status
Categories
(Marketplace Graveyard :: Developer Pages, defect, P4)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: krupa.mozbugs, Assigned: kngo)
References
()
Details
steps to reproduce:
1. Tester has an existing app which is incomplete from step 3
2. Click on the app from My Submissions page to complete the app submission process
3. Fill the required fields in Step 3 and click Continue
4. Step 4 indicates that the app needs a content rating
5. From the side menu, click on Status link
expected behavior:
App is still set to incomplete since content rating is not set up
observed behavior:
App status is set to 'Pending review' without a content rating
https://marketplace.allizom.org/developers/app/test-app-aardvark89/status
https://marketplace.allizom.org/developers/app/test-app-aardvark89/content_ratings/edit is empty
https://marketplace.allizom.org/reviewers/apps/review/test-app-aardvark89 The app shows up in the review queue without content rating
| Assignee | ||
Comment 1•12 years ago
|
||
I can't reproduce this with a new app, free or paid. I'm looking at the code, can't see how this happen.
This shouldn't be an issue for existing apps since warnings should display everywhere about needing a content rating else the app will be disabled by April 15. If it's an widely-affecting issue, may I have a screencast?
Updated•12 years ago
|
Priority: -- → P4
| Assignee | ||
Updated•12 years ago
|
Keywords: steps-wanted
| Assignee | ||
Updated•12 years ago
|
Keywords: steps-wanted
| Reporter | ||
Comment 2•12 years ago
|
||
This is on my list to provide reliable STR
Updated•12 years ago
|
Keywords: steps-wanted
| Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Comment 3•11 years ago
|
||
Issue is resolved - clearing old keywords - qa-wanted clean-up
Keywords: steps-wanted
You need to log in
before you can comment on or make changes to this bug.
Description
•