Closed
Bug 788394
Opened 12 years ago
Closed 12 years ago
Rejected updated version needs better instruction or flow of what to do next
Categories
(Marketplace Graveyard :: Developer Pages, defect, P3)
Tracking
(Not tracked)
RESOLVED
INVALID
2012-10-04
People
(Reporter: robhudson, Assigned: robhudson)
References
Details
Attachments
(1 file)
218.45 KB,
image/png
|
Details |
Similar to bug 788381, but for packaged apps that have a new version that has just been rejected.
We need some flow for the user to re-upload to resubmit the app for follow-up review. Again, this may be solved in AMO but I need to look.
Assignee | ||
Comment 1•12 years ago
|
||
Updated•12 years ago
|
Priority: -- → P3
Comment 2•12 years ago
|
||
AMO asks a user to upload a new version if it doesn't pass review. That sounds fine for apps as well. The solution in bug 788381 would be interesting, but I think the reviewers want to keep old versions around to make sure things were changed correctly.
Comment 3•12 years ago
|
||
The attachment looks like what needs to be there - is there more flow needed?
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → robhudson.mozbugs
Target Milestone: --- → 2012-10-04
Assignee | ||
Comment 4•12 years ago
|
||
Since we want to keep versions for comparison, this looks fine to me. Closing.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•