On Feb 19, 2008, at 1:28 PM, Mathew Snyder wrote:
> What kind of time frame are we looking at delivery on this? I've
> been holding
> off on writing complex reports while I figure out how to create
> another
> interface for it. However, if these reports will be available in
> the next 6
>
What kind of time frame are we looking at delivery on this? I've been holding
off on writing complex reports while I figure out how to create another
interface for it. However, if these reports will be available in the next 6
months I can probably convince my boss that my delays are justifiable.
Not sure this qualifies as a wishlist, but more Munin plugins like this
would be useful:
http://stats.koumbit.net/koumbit.net/lethe.koumbit.net.html#Rt
The source for those is available in:
https://lethe.koumbit.net/svn/koumbit/trunk/munin-plugins/
--
Rock journalism is people who can't write
On 2/14/08, Jesse Vincent <[EMAIL PROTECTED]> wrote:
> Hi Everybody,
>
> I have an RT hacker working on a new, expanded reporting tool for RT.
> While I can't promise that we'll implement _every_ report you want, we
> could really use your wishlists.
>
> What reporting and statistics do you want to
Samuel P. Howard wrote:
> Hi Jesse!
>
> I've seen a lot of really great ideas come from this request so far, so
> hopefully I can ask for something good, too. :)
>
> Following on a request from a previous e-mail, we could really use the
> ability to report on tickets and get a breakdown in "Time
as a minimum at least what rt-statistics does.
http://wiki.bestpractical.com/view/RT3StatisticsPackage
jamie
> Jesse Vincent wrote:
> Hi Everybody,
>
> I have an RT hacker working on a new, expanded reporting tool for RT.
> While I can't promise that we'll implement _every_ report you want, w
On Sat, 2008-02-16 at 15:26 -0500, Mathew wrote:
> The ability to create customized reports. Perhaps by selecting the
> fields we want, the criteria to match against, type of graph, etc.
> Having a large set of predefined reports is great and will be highly
> appreciated on our end but sometimes y
The ability to create customized reports. Perhaps by selecting the fields we
want, the criteria to match against, type of graph, etc. Having a large set of
predefined reports is great and will be highly appreciated on our end but
sometimes you want a one-off or something that isn't provided.
Hi Jesse!
I've seen a lot of really great ideas come from this request so far, so
hopefully I can ask for something good, too. :)
Following on a request from a previous e-mail, we could really use the
ability to report on tickets and get a breakdown in "Time Worked" per RT
user/technician.
S
On Thu, 2008-02-14 at 09:52 -0500, Jesse Vincent wrote:
> I have an RT hacker working on a new, expanded reporting tool for
> RT.
> While I can't promise that we'll implement _every_ report you want,
> we
> could really use your wishlists.
>
> What reporting and statistics do you want to get o
Jesse,
A couple thoughts. If a report module was just that, a completely
independent set of code and DB Tables, then historical milestones of
data (like monthly, yearly, etc.) could be stored, creating a tremendous
foundation for many types of reports. As a "self-contained" module, it
Jesse,
I would add to the time-tracking part. Perhaps a new table or two that
contain various time totals (hours for a ticket per CF Org code for a
month/year, etc.) so the actual time spent on a ticket per month can be
tracked to show monthly/yearly trends/statistics.
Kenn
LBNL
On 2
On Thu, Feb 14, 2008 at 09:52:52AM -0500, Jesse Vincent wrote:
> Hi Everybody,
>
> I have an RT hacker working on a new, expanded reporting tool for RT.
> While I can't promise that we'll implement _every_ report you want, we
> could really use your wishlists.
>
> What reporting and statistic
Hi!
I would like a report for a year, which
report how long tickets with the subject
"foo*" in the Queue x were in the states new,
open or stalled
All these tickets could have sub tickets (children)
in the queue y and z. All these direct children
should also be evaluated.
The report should cons
Jesse,
What my group really wants is a way to generate weekly status reports from
RT. I.e. a report of ticket/task activity with all the transaction comments.
Not a finished report, but something that could be dropped into a text
editor and cleaned up for the public.
I know I could do this with the
On Thu, Feb 14, 2008 at 09:52:52AM -0500, Jesse Vincent wrote:
> Hi Everybody,
>
> I have an RT hacker working on a new, expanded reporting tool for RT.
> While I can't promise that we'll implement _every_ report you want, we
> could really use your wishlists.
>
> What reporting and statistic
Hi,
I'm a recent user/admin of rt, which was already setup in my new
company, so I don't know much about the historical of RT.
What I'm wishing, I don't even know if it's technically feasible, is
that when you reply to a ticket, the email that it sends is interpreted
as a "reply", so that my mail
Reporting - We need your wishlists
Problem Trending :-)
I understand the difficulties of implementing this, not least that problem
categories vary in definition from company to company, but basically: A
report based on a custom fields in a ticket, where the organisation creates
a custom field for
2
8
Total Work Orders 18 10
28
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jesse
Vincent
Sent: Thursday, February 14, 2008 9:53 AM
To: Users rt-Users
Subject: [rt-users] RT Reporting - We need your wishlists
Hi Everybody,
Historical looking reports:
-Status History per ticket (Default new->open->stalled->resolved)
-Geneology (show the status history of a ticket along with it's nested
children & grand children or other dependancy tickets (great for
tracking approvals!))
-A report that spits out the history of a ti
At Thursday 2/14/2008 09:52 AM, Jesse Vincent wrote:
>Hi Everybody,
>
>What reporting and statistics do you want to get out of RT?
- Reporting by requestor metadata (e.g. Organization). QB allows for
filtering, but not for including these fields in the result set.
- Various time-period measuremen
Jesse Vincent wrote:
> Hi Everybody,
>
> I have an RT hacker working on a new, expanded reporting tool for RT.
> While I can't promise that we'll implement _every_ report you want, we
> could really use your wishlists.
>
> What reporting and statistics do you want to get out of RT?
This is
Ability to generate reports on tickets history.
For instance:
1- How much time a staff member worked on all tickets in the last month.
2- All open tickets which were replied from Jan to Mar.
3- All open tickets with specific custom field that was changed from Sep to Dec.
4- Who was the owner of Tic
Oooo! Cool, thanks! :-)
T.
On Thu, Feb 14, 2008 at 5:23 PM, Ruslan Zakirov <[EMAIL PROTECTED]>
wrote:
> Afaiu it's in RT already :)
>
> Tickets -> build search with defined queue condition -> show results
> -> chart grouped by custom field xxx -> go
>
> On Thu, Feb 14, 2008 at 6:10 PM, Traiano
Afaiu it's in RT already :)
Tickets -> build search with defined queue condition -> show results
-> chart grouped by custom field xxx -> go
On Thu, Feb 14, 2008 at 6:10 PM, Traiano Welcome <[EMAIL PROTECTED]> wrote:
> Problem Trending :-)
>
> I understand the difficulties of implementing this, n
Problem Trending :-)
I understand the difficulties of implementing this, not least that problem
categories vary in definition from company to company, but basically: A
report based on a custom fields in a ticket, where the organisation creates
a custom field for problem categories and then draws
Hi Everybody,
I have an RT hacker working on a new, expanded reporting tool for RT.
While I can't promise that we'll implement _every_ report you want, we
could really use your wishlists.
What reporting and statistics do you want to get out of RT?
_
27 matches
Mail list logo
