When generating a queue in the GUI, it adds a new entry to the config/queue/queues.generated.toml file with the [db-N] name:
[db-1]
name = "Customer calls back"
...
However, in the Routing section, when selecting a Queue as a route target, it asks for a path to a configuration file instead of the ID/name of the queue. Thus, forcing the user to manually modify the config files:
Proposal: use IDs and internally find the correct config, like the trunk selector does.
When generating a queue in the GUI, it adds a new entry to the
config/queue/queues.generated.tomlfile with the [db-N] name:However, in the Routing section, when selecting a Queue as a route target, it asks for a path to a configuration file instead of the ID/name of the queue. Thus, forcing the user to manually modify the config files:
Proposal: use IDs and internally find the correct config, like the trunk selector does.