Change Details

The OAuth extension allows a developer to propose a consumer, then use the proposed consumer on their own account for testing purposes before it is approved. This has led to a lot of "test consumer, do not approve" applications building up in the queue for consumer applications. We should break these off into their own separate section so that it's clearer how many consumer requests are actually waiting. -------------------------- **Version**: unspecified **Severity**: enhancement

The OAuth extension allows a developer to propose a consumer, then use the proposed consumer on their own account for testing purposes before it is approved. This has led to a lot of "test consumer, do not approve" applications building up in the queue for consumer applications. We should break these off into their own separate section so that it's clearer how many consumer requests are actually waiting. New consumers should be created in an "under development" stage and the developer should have to move them manually into the "proposed" stage.

The OAuth extension allows a developer to propose a consumer, then use the proposed consumer on their own account for testing purposes before it is approved. This has led to a lot of "test consumer, do not approve" applications building up in the queue for consumer applications. We should break these off into their own separate section so that it's clearer how many consumer requests are actually waiting. -------------------------- **Version**: unspecified **Severity**: enhancementNew consumers should be created in an "under development" stage and the developer should have to move them manually into the "proposed" stage.