Articles per agent report or graph with widget on dashboard
Moderator: crythias
Articles per agent report or graph with widget on dashboard
Hello there,
I am looking at creating a stats (preferably a widget with nice graphics on the dashboard) that will show me articles created by agents per day (week, month, year). Is it possible to dig out such a report with the current stats module?
Also, it would be a good idea if I am able to list top performers based on article numbers.
Thanks in advance.
I am looking at creating a stats (preferably a widget with nice graphics on the dashboard) that will show me articles created by agents per day (week, month, year). Is it possible to dig out such a report with the current stats module?
Also, it would be a good idea if I am able to list top performers based on article numbers.
Thanks in advance.
OTRS 3.3.6 with ITSM 3.3.6 running on CentOS 6.4, PostgreSQL 9.x
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Articles per agent report or graph with widget on dashbo
So, spamming a ticket = more productivity than a single article resolving it?xax0 wrote:it would be a good idea if I am able to list top performers based on article numbers.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Re: Articles per agent report or graph with widget on dashbo
I think that per-Agent statistics are disabled by default. As far as I know this is done for legal/privacy reasons accordingly to some country legislation. You should find the proper parameter on SysConfig to enable them (Frontend::Agent::Stats => Stats::UseAgentElementInStats = yes).
I can't help you on the second topic but I'm also interested on it.
@crythias: you are right but we are doing what boss asks us, though they are stupid requests
I can't help you on the second topic but I'm also interested on it.
@crythias: you are right but we are doing what boss asks us, though they are stupid requests

Last edited by dolfiz on 22 Jan 2014, 13:05, edited 1 time in total.
OTRS 3.3.3 - Ubuntu server 12.04 - MySQL
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Articles per agent report or graph with widget on dashbo
I'd be more interested in number of closed tickets and a lower number of articles per closed ticket = better.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Re: Articles per agent report or graph with widget on dashbo
@crythias: so, is there a way to extract number of articles per ticket? With a query this is easy but I can't find a way to build such a report with the built-in functionalities
OTRS 3.3.3 - Ubuntu server 12.04 - MySQL
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Articles per agent report or graph with widget on dashbo
Not that I'm aware of via statsdolfiz wrote:@crythias: so, is there a way to extract number of articles per ticket? With a query this is easy but I can't find a way to build such a report with the built-in functionalities
Last edited by crythias on 22 Jan 2014, 17:43, edited 1 time in total.
Reason: removed opinion. addressed question.
Reason: removed opinion. addressed question.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Re: Articles per agent report or graph with widget on dashbo
Thank you for the clarification
OTRS 3.3.3 - Ubuntu server 12.04 - MySQL
Re: Articles per agent report or graph with widget on dashbo
The idea is to see how much effort the agents are putting to resolve tickets. Also, if I am able to check on their interactions, I will be able to comment and audit their work.crythias wrote:So, spamming a ticket = more productivity than a single article resolving it?xax0 wrote:it would be a good idea if I am able to list top performers based on article numbers.
Can you suggest any useful PostgreSQL reporting tool that I can use to produce such reports?
Thanks a lot.
OTRS 3.3.6 with ITSM 3.3.6 running on CentOS 6.4, PostgreSQL 9.x
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Articles per agent report or graph with widget on dashbo
I cannot suggest any database specific reporting tool, because you still need a query.
Roughly, it would be select count of articles, create by, TicketID from article where create time between start and end group by TicketID, createby
Probably also throw in something where it detects that it's an agent article.
Roughly, it would be select count of articles, create by, TicketID from article where create time between start and end group by TicketID, createby
Probably also throw in something where it detects that it's an agent article.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
[SOLVED] Articles per agent report or graph with widget
I found out that Eclipse BIRT is quite useful tool for that purpose. It requires Tomcat server but looks like I am going to take use of its extensive reporting.
I will mark it as solved.
Thank you crythias!
I will mark it as solved.
Thank you crythias!
OTRS 3.3.6 with ITSM 3.3.6 running on CentOS 6.4, PostgreSQL 9.x
-
- Znuny newbie
- Posts: 1
- Joined: 21 May 2015, 02:43
- Znuny Version: Business Solution 4
Re: Articles per agent report or graph with widget on dashbo
Interestingly, so am I. However, I need to know which of my employees are closing tickets with fewer articles and which are doing many. That's exactly why this feature would be very helpful.crythias wrote:I'd be more interested in number of closed tickets and a lower number of articles per closed ticket = better.
My company uses OTRS as a support ticket system for our client base. If I want to know in total how many answers each of my employees sent out in a day, there is currently no way of knowing. There is no way of determining their first response resolution rate either, as far as I can tell. These are all very important metrics for managing a support centre.
I do hope such features are added. Even if crythias doesn't think it would be useful, clearly many of us do.
Re: Articles per agent report or graph with widget on dashboard
Getting a report on the number of articles per Ticket should be possible using:
Those numbers are far off from the reality of what's actually present in our system here.
Trying now to find out why this happens instead of reporting actual numbers.
- Dynamic-Object: TicketAccountedTime
- X-axis/Evaluation by: Number of Articles
Code: Select all
QueueA: 0
QueueB: 0
QueueC: 5
QueueD: 0
Trying now to find out why this happens instead of reporting actual numbers.