-
Notifications
You must be signed in to change notification settings - Fork 32
🎨 [Frontend] Use Number of Seats defined in the Pricing Unit #7273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🎨 [Frontend] Use Number of Seats defined in the Pricing Unit #7273
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sweet! :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
|



What do these changes do?
The number of seats was extracted from the name of the pricing unit, too bad.
After this PR, the
num_of_seatsis actually moved to it's own field in the extraInfo and now the frontend uses this field. The Pricing unit creation was also updated and now a License classified units can be created.Related issue/s
num_of_seatsto pricing unit (for LICENSE type pricing plan) #7271How to test
Dev-ops checklist