Natively "upgrade" To A Package In A Different Group

[Jonathan]

Blesta should have the capability to allow upgrades between package groups in the admin interface.

 

Here's a usage scenario:

 

Packages 1-7 are all interchangeable and can upgrade between each other by admin & client.  They belong to the same package group.

Packages 8-11 are all interchangeable and can upgrade between each other by admin & client.  They belong to the same (second) package group.

 

Package 2 wants to upgrade to package 8.  No problem, it just needs to be moved to different hardware since it's a different type of hosting package (SSD package versus HDD package but otherwise identical).

 

There's no way to cleanly upgrade this person whereas there should be.  This is a non-issue in all competing products I'm aware of.

 

Since a hardware migration on the back-end is required, obviously we don't want the client doing this but forced package changes such as this should definitely be possible by an admin where you might want to override a normal scenario or end up in a situation like above.

[Paul]

Upgrades are currently limited to packages in the same group of the same module. I suppose this would technically be possible across package groups, if the module is also the same, as the primary limitation is the module. (It's not, nor will it ever be possible to upgrade to a package of a different module)

 

How do you propose this should look in the UI?

[Jonathan]

I'd not expect them to ever be able to cross modules.  That'd simply be unreasonable and I can't think of a usage scenario for that since you're have to be actually changing products or something.

 

Perhaps in the UI (admin side) there should be a separate dropdown for plans belonging to other package groups, perhaps triggered/displayed by clicking a button which turns into the dropdown which could override the main dropdown thus letting you "force" the package over to one from a different group?  This would let everything else be handled inline as it should be.  Compatible configurable options would move over, ajax would update page to add/remove them accordingly, etc.

 

On the other hand, instead of a button and completely different dropdown it could just be a tickbox that'd simply update the existing dropdown with the "override" options aka plans from other package groups?