Skip to main content
In progress : Included in Product Roadmap

Business rules for problems

Related products:Freshservice
  • November 29, 2022
  • 6 replies
  • 267 views

LucasNeiva_BR
Apprentice
Forum|alt.badge.img

It would be very interesting if there were business rules for problems as well. Currently, there are only rules for tickets, changes and service requests.

6 replies

Forum|alt.badge.img+3
  • Contributor
  • January 19, 2023

I recently ran into a good use case for business rules for problems as well. Upvoted.


Forum|alt.badge.img+5
  • Contributor
  • August 1, 2023

Our org is very disappointed that there is no Business form rules for Problem forms.  We are just getting started without implementation and have already found this to be an issue - and inconsistent with the other forms, Tickets, Services, and Change

We want to use the shared Categories field from Incidents, however, not all categories would be a problem so we need to set options to show that would be a potential problem.

We also want to use this form for Security issues. An incident is raised by the requester, the agent reviews and decides this is a potential security problem and raises a problem ticket. A security problem ticket will have many other fields related to a security problem vs other category problems and we can not show or hide those fields without business form rules.

We also need to mandate a particular field depending on the status of the ticket. 

None of these things can be done without Business Form Rules.


Forum|alt.badge.img+1
  • Contributor
  • September 27, 2023

I agree! 

We are currently running into issues where we have different Agent Groups that need to be involved in particular Problems. Unfortunately, you can only associate one group to that problem or Workspace. It would be nice to be able to select multiple Groups/Workspaces who need to be involved in those fixes.

 

We also had to create a full workflow to connect Freshservice to ClickUp - Our developers use this tool constantly when they need to implement these Problems into their sprints. 

 

Any finally, having to set a mandatory Requester is not useful in our business use case as our developers are generally the ones creating these Problems - Having them set the Requester as themselves and also the Agent doesn’t make sense. If our Problem is associated to an external partner, they do not have access to the progress of these tickets, nor are they able to even be set as a Requester...so it really makes no sense for our business.


alyssia.correa
Skilled Expert
Forum|alt.badge.img+8
New IdeaIn progress : Included in Product Roadmap

Forum|alt.badge.img+5
  • Contributor
  • January 6, 2025

Any indication on when this will be implemented?


Forum|alt.badge.img+7
  • Skilled Expert
  • April 2, 2025

Following this as well. Business Rules for Problems would be ideal.