Multiple Related List conditions are not working in report filters

[Mahesh Kumar2]

I am trying to create a report on incident table based on SLAs. I need to apply SLA business elapsed time explicitly for each priority in conditions. So in related list conditions i am trying to add multiple new criteria on task SLA table to fetch the data. I am getting for only 1 set of conditions. If i add new criteria conditions for another priority - No data is displaying. Can any one help. I am attaching the screenshots.

I am getting required data in above scenario.

But if i click new criteria in related list conditions and give filters for another priority as shown above in the screenshot - Result is, No Data to Display. Any mistake in my filter conditions. Can anyone help?

[Mark Manders]

We don't have access to your data, but if it's there, it should show.
But: why not remove the priority from the related list condition, because it feels like it's a very heavy query (you are querying the incident table through related lists of other tables, finding the incident table through task to get the priority). Why not just leave that part out and instead find the sla definition for that priority? 
And since you are looking for resolved tickets, you can also add the sla stage to the query (paused or completed).

[Mahesh Kumar2]

Hi Mark, Thanks for the inputs, but i need to apply custom filter for business elapsed time for each priority as you can see the screenshot, Hence i am using multiple condition criterias. So won't this work if i apply multiple criterias of related list conditions in single report?

[Mark Manders]

I think you need to turn it around, like Tsura says: get everything from the task_sla table. You have full access to everything on the SLA table. Related list conditions are already expensive, performance wise, and I think your solution to fulfill the requirement is just not taking.

[Mahesh Kumar2]

Hi Mark, thanks for the suggestion. I agree. But as i explained in Tsura's reply, I have multiple SLA records on some incidents. Is there a way to handle it so i can consider only Latest SLA record?