Aging for Closed Tickets but Open at the End of Particular Month

[BeIntel]

Hello All,

I am trying to create a report, where I'd like to show the total count of open tickets (backlogs) at the end of each month irrespective of current status as shown below:

Current Calendar Month	0-5 days	6-10 days	11-30 days	>1 Month	> 3 months	> 6 months	Escalated	Grand Total
IT Support Team [without Alerts]	307	174	391	489	275	115	17	1751
SD Team 1	132	34	38	20	0	0	1	224
SD Team 2	63	16	24	9	3	0	0	115
SD Team 3	2	2	1	0	0	0	0	5
SD Total	197	52	63	29	3	0	1	344
IT Total	307	174	391	489	275	115	18	2095
SD Backlog Efficiency	64.17%	29.89%	16.11%	5.93%	1.09%	0.00%	5.56%	16.42%

New Date for Aging - If the ticket hasn't been resolved, eomonth date is considered for calculating Backlog age else resolved date is considered. I have put a sample data below to explain the scenario better. Please check and let me know, if you require any additional info.

Is there an easy way to find out the backlog age instead of creating new 6 columns to find the backlog age?

Ticket Key	Created Date	Resolved Date	EOM (based on created date)	New Date for Aging	Aging on eom Jul 23	New Date for Aging	Aging on eom Aug 23	New Date for Aging	Aging  on eom Sep 23
CC1	05-Jul-23	02-Oct-23	31-Jul-23	31-Jul-23	26	31-Aug-23	57	30-Sep-23	87
CC2	05-Jul-23		31-Jul-23	31-Jul-23	26	31-Aug-23	57	30-Sep-23	87
CC3	05-Jul-23		31-Jul-23	31-Jul-23	26	31-Aug-23	57	30-Sep-23	87
AB1	01-Aug-23	01-Aug-23	31-Aug-23			01-Aug-23	0	01-Aug-23	0
AB2	01-Aug-23	05-Sep-23	31-Aug-23			31-Aug-23	31	05-Sep-23	36
AB3	01-Aug-23	01-Aug-23	31-Aug-23			01-Aug-23	0	01-Aug-23	0
AB4	01-Aug-23		31-Aug-23			31-Aug-23	31	30-Sep-23	61
AB5	02-Sep-23	02-Sep-23	30-Sep-23					02-Sep-23	0
AB6	02-Sep-23	02-Sep-23	30-Sep-23					02-Sep-23	0
AB7	02-Sep-23	02-Oct-23	30-Sep-23					30-Sep-23	28
AB8	02-Sep-23	02-Oct-23	30-Sep-23					30-Sep-23	28
AB9	02-Sep-23	02-Oct-23	30-Sep-23					30-Sep-23	28

[giammariam]

Hi @BeIntel, I'm trying to make sure I understand the scenario. Is your source dataset structured with the following fields? 

Ticket Key

Created Date

Resolved Date

And then are these fields ones that you created to try to solve the problem?

EOM (based on created date)

New Date for Aging

Aging on eom Jul 23

New Date for Aging

Aging on eom Aug 23

New Date for Aging

Aging  on eom Sep 23

I'm happy to help, I just want to be sure that I understand what you're after. 

If you are able to provide a sanitized .pbix file (here's how) structured similarily to your actual .pbix, it'd be a huge help.

[BeIntel]

Hi @giammariam , yes you're right. I have a data with the fields - Ticket#, Created, Resolved, Status.

Trying to find out the backlog of each month (at the end of month while selecting in slicer) with aging slots irrespertive of current status of the ticket.