Description -
The current functionality for routing rules is very limited. We are only able to configure routing rules for specific queue topics. Allowing us to assign specific user/teams to a specific queue topic.
The following is functionality that is possible through Fusion, but want to be available without Fusion:
1. Automatically Convert Requests/Issue into a Project
If a request is submitted through a specific queue topic, then automatically convert the request into a project using a specific project template. Ideally, we would also have the ability to configure this at the custom form level. e.g. If the requester selects XYZ on the request form, then convert into a project using XYZ template. If the requester selects ABC on the request form, then convert into a project using ABC template.
2. Dynamic Request Routing Based on how the Form was Completed
Similar to #1, allow us to set routing rules based on how the request form was completed. If certain custom fields options are selected, then we are able to configure routing options such as a) assign the request to a specific user(s), b) convert the request into a project using a specified template, c) send a customized notification to specific users/roles d) automatically set the status of the request to a specific status, e) remove specified tasks from the converted project, etc.
Why is this feature important to you -
Ultimately, we're looking for more out-of-the-box functionality to configure dynamic routing based on how the request form was completed. Requiring Fusion to meet these needs places extra cost and time on the customer to build missing functionality that we believe should already be included. This functionality would reduce the amount of work/steps for our teams. These are repeatable and predictable steps that can be automated. This functionality is currently available on competitor systems (Asana, ClickUp, etc.).
