You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
While there is sense in treating the run limit separately (e.g. it is better to round the price per project before multiplying by the license number), it is an essential piece of information, for example when picking a license in the course interface:
There is no way here to understand which license has to upgrade many projects in a "typical" use case of one instructor license and one student license. One has to remember the correspondence of keys or give appropriate titles. Admins suffer as well ;-)
Expected behavior
In some places it is possible to expand the license information and see the run limit, how many projects it is applied to, and how many are running. Maybe the last two numbers are expensive to compute and should not be shown everywhere, but run limit is present in the license data and it has to be more exposed.
The text was updated successfully, but these errors were encountered:
Describe the bug
While there is sense in treating the run limit separately (e.g. it is better to round the price per project before multiplying by the license number), it is an essential piece of information, for example when picking a license in the course interface:
There is no way here to understand which license has to upgrade many projects in a "typical" use case of one instructor license and one student license. One has to remember the correspondence of keys or give appropriate titles. Admins suffer as well ;-)
Expected behavior
In some places it is possible to expand the license information and see the run limit, how many projects it is applied to, and how many are running. Maybe the last two numbers are expensive to compute and should not be shown everywhere, but run limit is present in the license data and it has to be more exposed.
The text was updated successfully, but these errors were encountered: