Closed Bug 951452 Opened 11 years ago Closed 11 years ago

"Approved but waiting" apps don't appear in China queue

Categories

(Marketplace Graveyard :: Reviewer Tools, defect, P2)

x86
macOS
defect

Tracking

(Not tracked)

VERIFIED FIXED
2014-04-22

People

(Reporter: adora, Assigned: kngo)

References

Details

STR: 1. Create an app, deselect "publish as soon as app is approved" and add China region 2. Approve app in main Marketplace queue Expected: app then appears in China queue (for example, if developer wants to wait until all regions are approved before publishing) Actual: app doesn't appear in China queue until developer publishes app
In the current implementation, apps show up in the China queue only after they have been approved in the main review queue. But, I can see how that can be confusing for users.
(In reply to krupa raj[:krupa] from comment #1) > In the current implementation, apps show up in the China queue only after > they have been approved in the main review queue. > > But, I can see how that can be confusing for users. they *have* been approved in the main queue, but have an approved-but-waiting rather than a fully-reviewed status.
Priority: -- → P4
This should be higher than a p4 imo - it means apps that are approved but waiting (either because the developer has selected the option, or reviewers have changed platforms, etc) can never be approved for China because they don't show up in the queue.
Priority: P4 → P2
Component: General → Reviewer Tools
Assignee: nobody → kngo
I have a fix for this but realized something. Won't they show up once the developer publishes them? The app will then become STATUS_PUBLIC, and then they can be approved in China, which makes sense since if the developer wants to wait, they shouldn't be approved in China.
Ah, I see "(for example, if developer wants to wait until all regions are approved before publishing)".
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2014-04-22
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.