Problems Functionality

UI Suggested Updates for Problems

We are presently using PROBLEMS quite heavily in our Org. One thing our teams have noticed is the restrictive functionality with Problems. Here is some feedback on some pain points for our teams

1. When you are trying to do a Bulk Update on tickets, there is no way to assign Problems to multiple tickets at once. When Bugs come in, we see a high increase of tickets, so to be able to assign the increase of tickets to a Problem from the Ticket Overview Page
2. Creating a VIEW option within the columns in Problems that showed the PRB ID would be extremely useful.  Currently the PRB number lives within the Subject Column and is at the end of the Subject. depending on the Problem Subject, it is usually cut off
3. When Associating a PROBLEM to a ticket, the Association UI is quite difficult to work with when there are multiple Problems
   1. The search functionality is not very good at finding tickets in the picklist. eg. typing “payment issue” in the search, we may get back 0 Results found, when there are a few different tickets that have the keyword Payment in the Subject Line - Where is this SEARCH BAR pulling the query from? (eg. Decription, Subject?)
   2. The list shows Closed problems. So if we are unable to find our PRB via the SEARCH option, we are stuck scrolling through all tickets within that Group.
4. Piggybacking off of 3.2 above, there is no way to set Business Rules and the Workflows are very limited in the Admin options.
5. When looking at ALL PROBLEMS, the system standard autofills to 6 MONTHS. It looks like this can only be edited by saving a new view of ALL PROBLEMS and setting that filter - this has resulted in many teams asking why their Problem has disappeared, and me needing to continuously explain why that happened and how to see the Problems outside 6 months.
6. And finally, this is more of a wishlist item for myself, but removing the mandatory Due Date field. For our developers.
   1. Our developers work in Sprints and pull in Bugs into their sprints (into ClickUp...via an integration with Zapier) as they have time/space to work on them. Within Freshservice, this Due Date is not managed at this level, but once it reaches their queues.

Thanks!