Cannot approve or reject application in the Needs Information state
Bug #983965 reported by
Andrew Mitchell
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Developer registration portal |
Fix Released
|
Medium
|
Danny Tamez |
Bug Description
The ARB needs to be able to reject applications that have been in the Needs Information state for some time, where the application submitter has not replied. There currently doesn't look to be any way to change the state from Needs Information for ARB reviewers, e.g. on https:/
summary: |
- Cannot reject application in the Needs Information state + Cannot approve or reject application in the Needs Information state |
Changed in developer-portal: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in developer-portal: | |
assignee: | nobody → Danny Tamez (zematynnad) |
status: | Confirmed → In Progress |
Changed in developer-portal: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Discussed with ajmitch.
Allowing reviewers to force NeedsInformation -> PendingReview sounds reasonable, as this is most often due to the developer intending to put the app back into the review queue, but failing to notice the subtly different side-effects of the "Resubmit for review" and "Send comment" buttons.
Another requested transition is NeedsInformation -> Rejected and NeedsInformation -> QAPending. These are trickier because they would usually require you to provide extra information (a reason for rejection, or a package name + supported distro arch series for approval). We could allow the former by just filling in a blank reason for the rejection, but I'd be more inclined to only allow NeedsInformatio n->PendingRevie w, and the reviewer can then take it from there, moving it forwards to Rejected or QAPending through the usual review process.