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
"Creation and Deletion of 'Subscriptions to QL' on the Creation and Deletion of Tenants"
Description:
Whenever a user creates tenants, subscriptions to QL should be automatically created for the tenant. For subscription creation, data relevant to subscription should only be provided, rest generic things like 'subscription QL internal URL' should be automated and the user shouldn't have an idea about the same. The same subscription should be deleted along with tenant deletion.
User Story:
"As a user, when I click on "Add Tenant", it should give me the provision to create multiple subscriptions. While creating subscriptions, only relevant data should be asked, rest generic data like 'subscription QL internal URL' should be automatically added."
"As a user, whenever I click on "Remove Tenant", it should also remove the subscriptions assigned to the tenant.
The text was updated successfully, but these errors were encountered:
Title:
"Creation and Deletion of 'Subscriptions to QL' on the Creation and Deletion of Tenants"
Description:
Whenever a user creates tenants, subscriptions to QL should be automatically created for the tenant. For subscription creation, data relevant to subscription should only be provided, rest generic things like 'subscription QL internal URL' should be automated and the user shouldn't have an idea about the same. The same subscription should be deleted along with tenant deletion.
User Story:
"As a user, when I click on "Add Tenant", it should give me the provision to create multiple subscriptions. While creating subscriptions, only relevant data should be asked, rest generic data like 'subscription QL internal URL' should be automatically added."
"As a user, whenever I click on "Remove Tenant", it should also remove the subscriptions assigned to the tenant.
The text was updated successfully, but these errors were encountered: