Join problem task to problem to incident to SLA creating a database view

Yanhong Huang
Tera Contributor

I am creating the database view to Join problem task to problem to incident to SLA that can be reported on for things like: Problem task associated with disruptive incident has breach SLA.

May I know how to achieve?

 

 

YanhongHuang_2-1720498036486.png

 

1 ACCEPTED SOLUTION

I don't think you need all 4 tables for that. It could be enough to join [problem_task] with [task_sla] and add a where clause to narrow the list down to just the problem tasks that are children of problems records associated with a disruptive incident.

 

To get an idea how to join [problem_task] with [task_sla], take a look at database views [incident_sla] or [problem_sla] that are available in the base system.

View solution in original post

5 REPLIES 5

Slava Savitsky
Giga Sage

It seems that you are trying to join 4 tables. Do you really need all of them in your database view? What attributes from each of those tables would you like the database view to display? Which table do your SLAs run on? And how do you define a "disruptive incident"?

yes, Join problem task to problem to incident to SLA , "disruptive incident" is a filed in Incident table

I need to get the problem task count, which under problem have link with disruptive incident, and need to count these problem task if have breach SLA (SLA created in problem_task table)

I don't think you need all 4 tables for that. It could be enough to join [problem_task] with [task_sla] and add a where clause to narrow the list down to just the problem tasks that are children of problems records associated with a disruptive incident.

 

To get an idea how to join [problem_task] with [task_sla], take a look at database views [incident_sla] or [problem_sla] that are available in the base system.