Monthly Indicator source, showing the same result every month

[veronica_malmo]

Hi all!

Another challenge here today..

I want to collect the score of how many open incidents an assignment group has every month. If I use the daily indicator, the numbers gets all wrong when I do a SUM by Month, because of course it adds all the records for each day together..

Then I thought of collecting only the incidents thar are open on the last day of the month, that way we can trach the backlog from month to month. I created an indicator source (Incidents.open.Monthly) and set the Valid for frequency to Monthly,   Fact table to Incident, conditions to: State is not one of: resolved, Closed.

Now I get the same result for every month, looking closer I can see that the records listed for January was not created until May so how is this possible? How to fix this? And do I have to create a job so it only collects once a month?

[brandimore]

Thank you Veronica! I believe we have the same requirement. To see the backlog of tickets (not closed) overtime for a period of time. Like you, I would like to collect the day the 1st of the month for the previous month. I believe Arnouds print screens were for daily refreshes, but maybe I'm missing something?

Did you end up going with this collection criteria on the Incidents table?

And for collecting the data, what did you put for the parameters?

One of the issues I'm facing is that I see for October I have a brand new ticket open and it's showing in the 06-30 age day grouping. This is after running the historical and above job. I'm not sure why it's not showing up in the 00-01 age grouping.

You mention: " Now instead of having a monthy indicator, I have a job that runs the first day of every month ``. Maybe if you could confirm what you mean, as indicators are based on indicator sources.

Thanks so much!

[veronica_malmo]

HI,

yes that looks like what I did. I first tried to create an indicator source and indicator with a monthly frequency, but that didn't work as I wanted it to, so therefore I created a collection job that only runs once a month. So your parameters and job looks like mine. I'm not sure how it can be placed in the wrong age group though..

[brandimore]

Thanks for the response. It makes no sense to me either! I logged a ticket with SN. They are looking and cannot find the problem yet. Some records drop in the right bucket but ones for October aren't so they are checking. I'll keep you guys posted on here as I wouldn't want anyone going through the same frustration as me.

[Arnoud Kooi]

I think your problem may be the setting:

Relative start interval and Relative end interval.   In the job settings.

Try setting this to month. Because you set this to day, you collect for a day in this month and the score_end date will be set to the last day of the current month.

Make sure you delete the scores for the indicator, by going to the scoresheet and hit the delete all scores button, before recollecting.

[brandimore]

Arnoud! Thanks for the input.

So how does this look?

Relative end 0 = as we don't have an end date.

Relative start 4 = based on our go live date.