Page MenuHomePhabricator
Create Task
Maniphest T7154

Allow administrators to cancel instances without staff intervention
Closed, ResolvedPublic
Actions

Description

Currently, you'd need to email us to cancel an instance. We should have a button that does it for you.

Revisions and Commits

Restricted Diffusion Commit

Event Timeline

epriestley created this task.Feb 4 2015, 2:36 PM
epriestley raised the priority of this task from to Needs Triage.
epriestley updated the task description. (Show Details)
epriestley added a project: Phacility.
epriestley moved this task to Backlog on the Phacility board.
epriestley added a subscriber: epriestley.
epriestley moved this task from Backlog to Do After Launch on the Phacility board.Feb 4 2015, 7:28 PM
epriestley claimed this task.Feb 20 2015, 4:01 PM

I'm going to implement a "Disabled" state which is just like "Suspended" but with different language ("Disabled" = disabled by owner [they don't want it anymore]; "Suspended" = disabled by staff [for nonpayment or TOS violations]).

We won't bill for "Disabled" instances. To prevent shenanigans, users will have to contact us to un-disable an instance. This should solve most of the real use cases until we have more sophisticated workflows here.

epriestley added a commit: Restricted Diffusion Commit.Feb 20 2015, 7:58 PM
epriestley added a subscriber: Mnkras.Feb 20 2015, 8:16 PM

I think this is sorted now. I disabled all my test instances and properly suspended @Mnkras's abusive, deceptive, TOS-violating, terrible, no-good secure.phacility.com.

Although maybe I'll just hard-code that to redirect to secure.phabricator.com, since it seems like anyone ending up there has a close to 100% chance of having intended to come here.

epriestley closed this task as Resolved.Feb 20 2015, 8:16 PM
Phabricator · Built by Phacility