Closed Bug 737727 Opened 12 years ago Closed 12 years ago

Add STATUS_REJECTED status for Marketplace

Categories

(addons.mozilla.org Graveyard :: Admin/Editor Tools, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: krupa.mozbugs, Assigned: cvan)

References

Details

When an add-on fails the review process, users can address all the issues and upload a new version and seek review again.

We need to figure out the workflow when an app fails review-

a) How do we notify the users regarding next steps? (via email of course, but we need instructions on how they can reapply)
b) What is the status of an app which has failed review?
c) How do we allow them to seek review after addressing all the issues related to their app?
d) Do we need to inform editors that app under question was rejected previously? (This will probably go under the 'App History' section)
e) When they seek re-review, do we want to allow app developers to be able to add notes to the Editors? (we allow this for add-ons)
f) Can an editor ever move an app to 'Disabled by mozilla' status?
Assignee: nobody → cvan
Target Milestone: --- → 6.4.8
Priority: -- → P1
Summary: What happens when an app gets rejected during review? → Add STATUS_REJECTED status for Marketplace
Whiteboard: [ddn]
Target Milestone: 6.4.8 → 6.4.9
Blocks: 743113
https://github.com/mozilla/zamboni/commit/446b2a7

Two caveats:
* Waiting Time (https://marketplace-dev.allizom.org/en-US/reviewers/queue/apps) is incorrect for re-applied apps, since we're not looking at when an app goes from REJECTED -> PENDING. (Filed bug 743113 for this.)
* Developer Reply (upon resubmission) gets overwritten if same version/manifest gets rejected twice (that is, goes from PENDING -> REJECTED -> PENDING -> REJECTED)! (This case I don't think is an issue. But if I'm mistaken, please do open a bug.)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.