Closed Bug 842831 Opened 13 years ago Closed 12 years ago

Allow reviewers to search by privileged packaged apps

Categories

(Marketplace Graveyard :: Search, defect, P2)

defect

Tracking

(Not tracked)

VERIFIED FIXED
2013-07-04

People

(Reporter: robhudson, Assigned: mat)

References

Details

(Whiteboard: [p=1])

We don't currently have a field for this in our index or track it in the database. But if we stored the "type" field of the manifest we could easily filter by this.
Blocks: 741513
Aware its a different bug, but indicating if the app is privileged with an icon in the queue and on the review page is much more important than being able to search for it, imo.
Depends on: 846420
Whiteboard: [p=1]
Priority: -- → P2
The icon was added to the queue page but we need to do this again for the search results. It should just be a matter of adding something like flags.push({suffix: 'packaged-app', title: gettext('Privileged App')}); in mkt/reviewers.js:buildAppResultRow() - I couldn't do this in bug 846420 because we didn't have latest_version in our index at the moment. See also bug 848446
Assignee: nobody → mpillard
Target Milestone: --- → 2013-07-04
Status: NEW → ASSIGNED
This was fixed in https://github.com/mozilla/zamboni/commit/0d71a0cc9d221616d282f00295eae281a72664dd But: it doesn't fully work, there was a fix that is part of bug 848446 (which will be fixed soon) that we need to make everything work correctly.
Status: ASSIGNED → NEW
Depends on: 848446
848446 is now fixed so this should work. Steps to reproduce: - Find/upload a privileged packaged app on -dev. - Load the reviewers tools advanced search - Find your app using the new "Privileged App" field. Also test that "Unknown" doesn't apply the filter and that "No" works as a filter value as well.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Verified as fixed in https://marketplace-dev.allizom.org/reviewers/apps/queue/ on FF25 (Win 7). Postfix screencast http://screencast.com/t/4ZggbSeh Closing bug.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.