Closed Bug 764878 Opened 12 years ago Closed 12 years ago

"Delete" option missing from "Manage Status" for some apps.

Categories

(Marketplace Graveyard :: Developer Pages, defect, P3)

Product:
Marketplace Graveyard
Component:
Developer Pages
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: vcarciu, Unassigned)

References

(
URL
)

Details

(Keywords: regression)

Prerequisites: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/16.0 Firefox/16.0a1 Steps to reproduce: 1.Go to https://marketplace-dev.allizom.org/en-US/developer/submissions 2.Open this app and go to "Manage Status" : https://marketplace-dev.allizom.org/en-US/developers/app/test-app-one/status Expected results: "Delete" and "Disable app" buttons are displayed. Actual results: "Delete" button is missing. Please see screencast for this bug: http://screencast.com/t/fh9aFaH5GZ Notes: 1.Not reproducible for all apps. "Delete" button is visible for the rest of my apps even if all apps are in the same state. 2.Both buttons are visible for admins. 3.I was not able to reproduce in production.
I see the "Delete App" button: http://cl.ly/1Y0o0C3q0y26322v4338
Assignee: nobody → cvan
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Target Milestone: --- → 2012-06-21
Still reproducible and "Delete" button is missing. As I said in bug notes, for admins both buttons are visible.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Priority: -- → P3
No longer blocks: 752013
Assignee: cvan → nobody
Blocks: 766201
OS: Windows 7 → All
Hardware: x86_64 → All
Target Milestone: 2012-06-21 → ---
Blocks: 766199
Is the problem that the button is missing for reviewers or developers?
No, the issue was reproducible for regular users.
No longer blocks: 766199
Is this still valid?
Not able to reproduce it anymore so I think that it was resolved.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Verified as fixed. Delete button present for all my apps.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.