Select Ticket Fields

Hi Tuan,
Thanks for the clarification — that helps! What you're describing makes sense, and you're right that there isn't a way to "save" the field configuration mid-setup the way you might expect.
When you add a new user and want them to receive text notifications, you don't need to create a new notification configuration each time. Instead, you can add them as a recipient on an existing notification.
Looking at your environment, you have many notifications with identical criteria that each have a single recipient — those could actually be consolidated into one notification with all recipients listed together. That way, when a new user needs to receive the same texts, you're simply adding them to an existing notification rather than building a new one from scratch each time.

To do this, locate one of your existing notification configurations, open it, and add the new user as an additional recipient alongside the others. Once consolidated, adding future users is just a matter of updating the recipient list on that one notification rather than creating a new configuration.

Does that help clarify? It won't fully resolve the inability to save a configuration mid-build for reuse, but consolidating your notifications would significantly improve your existing process.

Thanks for the suggestion! The Select Ticket Fields configuration is generally intended to be set based on the ticket fields you want included in your Ticket Notifications and retained for future use automatically as part of that saved configuration. You mentioned using this feature frequently and selecting the same seven fields each time. Can you provide a little more detail on what requires you to update your Ticket Notifications configuration daily, particularly if you’re selecting the same seven fields each time? Understanding the workflow you’re trying to accomplish will help us determine whether there’s an existing feature or process that better supports the use case, or if there’s an opportunity for improvement elsewhere.