Change request reporting

pramn
Kilo Sage

Hi Team , 

I like to show a daily count of CAB reviewed changes that were implemented (where filter can be adjusted to this week or this/last month) but gives also a total by month (closed) for past 12months

 

This chart compared and graphed with the total number of changes implemented (regardless of CR, CAB reviewed (approved/rejected/or not)

I created the following  but I must have grabbed wrong table or something because nothing displays.

pramn_0-1764737430822.png

The table i have used change _request

Can you please help me to fix this .

 

Thanks in advance !

1 ACCEPTED SOLUTION

Me Being Mustaq
Tera Guru

Hi @pramn ,

 

You’re very close; the issue is most likely the table selection and/or aggregation type, not the filter itself.

1. Use the correct table

For CAB-reviewed implemented changes, the safest source is the Change Request table:

  • Table: Change Request [change_request]

  • Filter (base idea, adjust field names as in your instance):

    • Active is false

    • State is Closed (or your “Implemented/Closed” state)

    • Implementation state is Implemented (if you track implementation separately)

    • CAB required is true

    • Closed is between [date range] (e.g., last 12 months)

If you accidentally used a task SLA, audit, or change_task table, you will often see a blank chart because the filter doesn’t match any rows.​

2. Daily count and 12‑month totals

Create one time series report and let it show daily counts plus monthly totals over the last 12 months:

  • Type: Time Series (Area, Column, or Line)

  • Group by: Closed (or Actual end), with Time series > Day and Stacking: Off

  • Aggregation: Count on Number (or sys_id)​

  • Time series duration:

    • Show: Last 12 months

    • Allow user to change: Yes (so they can switch to This week / This month / Last month in the filter)​

This will:

  • Plot daily counts of CAB‑required implemented changes.

  • When changing the time series granularity to Month, show a monthly total over the last 12 months from the same report.

3. Add comparison: all implemented changes

To compare CAB‑reviewed implemented vs all implemented:

Option A – Multiple‑series time series (preferred):

  1. Use table change_request.

  2. Add two conditions in the “Series” section or use a Breakdown / Split by:

    • Series 1: CAB required = true (CAB‑reviewed implemented).

    • Series 2: CAB required = false OR simply no CAB filter (all implemented).

  3. Same time field: Closed.

  4. Aggregation: Count.

This gives lines/bars:

  • Line/Bar 1: CAB reviewed implemented.

  • Line/Bar 2: All implemented changes for the same dates.​

Option B – Two separate reports on the same dashboard:

  • Report 1: CAB required = true (as above).

  • Report 2: No CAB filter (all implemented).
    Then place them side by side on a dashboard.​

4. Why “nothing displays” now

Common reasons a ServiceNow report shows nothing even though the filter looks fine:​

  • Wrong table (e.g., using “Change tasks” or “Change request – CAB delegate” instead of change_request).

  • Filter field names don’t exist on that table (Closed/State/CAB required might be from change_request only).

  • Time filter excluding all data (e.g., Closed between 11‑24 and 12‑07 but your closed dates are outside this range).

  • Chart type set to something incompatible with your grouping (e.g., time series without a date field in “Group by”).

As a quick test, run the same filter in the Change Request list (change_request_list.do), confirm you see records, and then build the report from that list using “Create report” so the correct table and conditions are guaranteed

 

Please refer to the below link:-

 

If it is helpful, please hit the thumbs button and accept the correct solution by referring to this solution in the future it will be helpful to them.

 

Thanks & Regards,

Mohammed Mustaq Shaik

View solution in original post

1 REPLY 1

Me Being Mustaq
Tera Guru

Hi @pramn ,

 

You’re very close; the issue is most likely the table selection and/or aggregation type, not the filter itself.

1. Use the correct table

For CAB-reviewed implemented changes, the safest source is the Change Request table:

  • Table: Change Request [change_request]

  • Filter (base idea, adjust field names as in your instance):

    • Active is false

    • State is Closed (or your “Implemented/Closed” state)

    • Implementation state is Implemented (if you track implementation separately)

    • CAB required is true

    • Closed is between [date range] (e.g., last 12 months)

If you accidentally used a task SLA, audit, or change_task table, you will often see a blank chart because the filter doesn’t match any rows.​

2. Daily count and 12‑month totals

Create one time series report and let it show daily counts plus monthly totals over the last 12 months:

  • Type: Time Series (Area, Column, or Line)

  • Group by: Closed (or Actual end), with Time series > Day and Stacking: Off

  • Aggregation: Count on Number (or sys_id)​

  • Time series duration:

    • Show: Last 12 months

    • Allow user to change: Yes (so they can switch to This week / This month / Last month in the filter)​

This will:

  • Plot daily counts of CAB‑required implemented changes.

  • When changing the time series granularity to Month, show a monthly total over the last 12 months from the same report.

3. Add comparison: all implemented changes

To compare CAB‑reviewed implemented vs all implemented:

Option A – Multiple‑series time series (preferred):

  1. Use table change_request.

  2. Add two conditions in the “Series” section or use a Breakdown / Split by:

    • Series 1: CAB required = true (CAB‑reviewed implemented).

    • Series 2: CAB required = false OR simply no CAB filter (all implemented).

  3. Same time field: Closed.

  4. Aggregation: Count.

This gives lines/bars:

  • Line/Bar 1: CAB reviewed implemented.

  • Line/Bar 2: All implemented changes for the same dates.​

Option B – Two separate reports on the same dashboard:

  • Report 1: CAB required = true (as above).

  • Report 2: No CAB filter (all implemented).
    Then place them side by side on a dashboard.​

4. Why “nothing displays” now

Common reasons a ServiceNow report shows nothing even though the filter looks fine:​

  • Wrong table (e.g., using “Change tasks” or “Change request – CAB delegate” instead of change_request).

  • Filter field names don’t exist on that table (Closed/State/CAB required might be from change_request only).

  • Time filter excluding all data (e.g., Closed between 11‑24 and 12‑07 but your closed dates are outside this range).

  • Chart type set to something incompatible with your grouping (e.g., time series without a date field in “Group by”).

As a quick test, run the same filter in the Change Request list (change_request_list.do), confirm you see records, and then build the report from that list using “Create report” so the correct table and conditions are guaranteed

 

Please refer to the below link:-

 

If it is helpful, please hit the thumbs button and accept the correct solution by referring to this solution in the future it will be helpful to them.

 

Thanks & Regards,

Mohammed Mustaq Shaik