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
Summary of slack conversation: (listing this here for your later reference).
from Bob: importing multiple pricing tiers per TLD, that'll need to be added to the issue tracker, with ETA TBD this new feature of course, opens up a whole can of worms: Should there be conditional rules per tier? I think the first step is UX discovery about how to best manage the experience. because the current TLD import view handles mass updates (relatively) well.. I would hate to over-complicate it with more drop-downs and price markup features.
My current brainstorm shows me that there should be a new view before the current bulk TLD price view: A chooser for how you manage domains, 1 price per registration period, or multiple prices per registration period
Summary of slack conversation: (listing this here for your later reference).
from Bob: importing multiple pricing tiers per TLD, that'll need to be added to the issue tracker, with ETA TBD this new feature of course, opens up a whole can of worms: Should there be conditional rules per tier? I think the first step is UX discovery about how to best manage the experience. because the current TLD import view handles mass updates (relatively) well.. I would hate to over-complicate it with more drop-downs and price markup features.
My current brainstorm shows me that there should be a new view before the current bulk TLD price view: A chooser for how you manage domains, 1 price per registration period, or multiple prices per registration period
Ticket request by client:
https://mycircletree.com/client-area/ct-admin/supporttickets.php?action=view&id=5002
The text was updated successfully, but these errors were encountered: