3scale/issues-test — Issue #570: Non-critical bugs in MT 
Author: HakubJozak
Created: 2012-02-13 18:11:17+00:00
State: open

The critical bugs were sent by email. These are bugs that need to get fixed asap but are non-blocking for the deployment of MT.

Tasks
- Service plan changing rules in on "Usage Rules"

https://developer-admin.musixmatch.com/admin/site/usage_rules/edit

Should not be in API > Service? Service plans depend on services.
- https://developer-admin.musixmatch.com/admin/site/usage_rules/edit

Service user login area, the title is missleading, the two options in musixmatch

Allow user to regenerate access keys?
At least one application key is mandatory?

Are for backend v2, they should be greyed out if in v1

*_enabled switches
- https://developer-admin.musixmatch.com/admin/buyers/accounts?search[state]=&search[query]=buyer&search[country_id]=&search[plan_id]=2774444517

When you want to change a plan on the bulk actions, the list of account plans contains two publish plans an dozens of custom plans from default. Impossible to know what's their costumization and the name is fixed, unusable.

Changing plans is always to "official" plans, costumized plans should not be offered as options.

That only happens on the bulk options. On https://developer-admin.musixmatch.com/admin/buyers/accounts/2878236726 the change plan is fine.

See also on applications, have not checked it myself.

- Update:
there is another issue here. When I try to delete a plan, it tells me that there is alreay on application. Fine, I went to search for it. It's now impossible to find it because there are more than 40 plans with costumizations and there are not even alphabetically sorted. It took me 5 minutes to find the damn application that was in that plan.

Sort alphabetially the lists. But leave the costum plans on the plan selector in /admin/buyers/applications

The costum plans on the plan selector of the bulk operations widgets has to go. Because you cannot move to a custom plan.

Custom plan should only have 1 application.

That raises a question, what happens to a costume plan, when a) the application is deleted (via the account) and when b) the application changes to a different plan. In both cases the costum plan should be removed.

custom plan has to have always one and only one object associated. If it disappears the costumization also should disappear.

- this goes for application, accounts, etc.

The name of the costum plan, cannot be only Custom + name of the plan, otherwise the listing on plans in /admins/buyers/application is unusable. It should be "name of the plan (custom, ID)", the ID is the name of the application or the account being costumized. That way sorting alphabetically also puts costum plans after the original plan)
- The alert:

Changing your domain out of *.3scale.net means that you already obtained the SSL certificates for your domain. If you do not have them or have questions about it better ping support@3scale.net. Do you want to proceed?

Should only appear when the "domain name" was not "domain" already. Otherwise it pops out when you try to edit unrelated things like "site control" and you make people freak out.
- when you create a new metric or method, and you use a system_name that has already been taken the error is

"there are problems with you data". That should be a different color, otherwise people will not realize and also should have info about the error in particular, in this case: system name already exists

Same goes for features
- "End Users Requirements" section title without any setting at all.

https://developer-admin.musixmatch.com/admin/apiconfig/services/1184431236/settings

When all the settings of a section are hiddend, in this case becasue there is not end-user-plans defined the title should also go away.

- Plan change requests workflow,

AS a buyer I request a plan change, after requesting it i get a message with:

musixmatch	Plan change request has been sent	January 28, 2012 17:01

Fine so far the provider, receives:

"API System: Plan change request", good

I go an change the plan from the url in the message.

As provider I get:

"API System: Application plan change", good. The same email I would have received as provider is changing plans was automatic.

But the buyer receives nothing else. He never know if the plan change requests has been done done or not.

https://www.pivotaltracker.com/story/show/24110473