Recent searches
No recent searches
Custom Statuses should not be visible and usable on all the forms when using the bulk edit functionality
Posted Nov 21, 2024
Currently when we use the bulk edit functionality custom statuses are visible and usable even for forms they should not be.
E.g.: we have a custom status called “On-hold - People Services” which should be available only on our “Knowledge Request” form.
But if I use the bulk edit functionality on ticket/tickets that use form different from the “Knowledge Request” one, I see and I can apply the “On-hold - People Services” status:


In our opinion this should not be allowed. Even if the custom statuses are visible when using the bulk edit functionality there should be some validation when the user saves the request to deny access to that status because it does not match the form.
Please, look into this feedback and consider applying the behavior change.
Thank you.
1
2 comments
Shawna James
Thank you for taking the time to provide us with your feedback. This has been logged for our PM team to review. For others who may be interested in this feature request, please add your support by upvoting this post and/or adding your use case to the comments below. Thank you again!
0
Samantha Ramirez
+1 We'd also like to be able to prevent form-based custom statuses from being applied to ineligible tickets via bulk edit.
0