Hi!
In order to get both requests and incidents, you'd have to report on the task table and filter to only include those two task types.
As for months, you have to use one of the "time series" report widgets. They are the ones which can show data grouped by dates and aggregated on month. Unfortunately a pivot table is not in the group of time series widgets. You could use bar chart that trends on "opened at" by month, and then stack the columns by location. It would be the information that you are looking for, but in a different format.
Or you could use a calculated field. If you are on the Quebec release there is a button on the configure tab which lets you create such a field. You could then use a substring function to create a field that only contains the month number from the "created" field:
The result would be that you can use this field as columns:
If you wanted the actual month names, you'd have to add a field containing the name to the table, and a solution for populating that field. For example a business rule.
If you have performance analytics though, you'd have much nicer looking report by using scorecards and a breakdown on location. It would look something like this, only with locations instead of priorities. No new fields or other changes to the table would be required:
Hi!
In order to get both requests and incidents, you'd have to report on the task table and filter to only include those two task types.
As for months, you have to use one of the "time series" report widgets. They are the ones which can show data grouped by dates and aggregated on month. Unfortunately a pivot table is not in the group of time series widgets. You could use bar chart that trends on "opened at" by month, and then stack the columns by location. It would be the information that you are looking for, but in a different format.
Or you could use a calculated field. If you are on the Quebec release there is a button on the configure tab which lets you create such a field. You could then use a substring function to create a field that only contains the month number from the "created" field:
The result would be that you can use this field as columns:
If you wanted the actual month names, you'd have to add a field containing the name to the table, and a solution for populating that field. For example a business rule.
If you have performance analytics though, you'd have much nicer looking report by using scorecards and a breakdown on location. It would look something like this, only with locations instead of priorities. No new fields or other changes to the table would be required:
