bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shiva Teja <shivate...@gmail.com>
Subject Re: [GSoC] Add Time Series #489 - Discussion
Date Wed, 01 May 2013 15:07:12 GMT
Looks like there has been a misinterpretation of the idea from my side.
I'll get back on the details again.

Regards,
Shiva Teja.


On Wed, May 1, 2013 at 8:05 PM, Shiva Teja <shivatejau@gmail.com> wrote:

> Hi Gary,
> Having one more page for reports might not make sense. So yes, I will be
> extending the existing reports framework.
>
> Regards,
> Shiva Teja.
>
>
> On Wed, May 1, 2013 at 7:55 PM, Gary Martin <gary.martin@wandisco.com>wrote:
>
>> On 01/05/13 15:00, Shiva Teja wrote:
>>
>>> Hi devs,
>>>
>>> Here's a list of reports that I'll be generating as a part of the
>>> project(Combining mine with the one's suggested by Joe and Gary.)
>>>
>>>   For visualising using graphs(very much similar to Ryan's
>>> TracTicketStats[1]):
>>>   * Number of tickets opened/closed etc in a period(weeks, months etc.)
>>> by
>>> all users or by a particular user.
>>>   * Number of tickets opened/closed by a user in a period or all time(I
>>> mean, the graph will contain number of tickets opened by each top
>>> users.).
>>>   * Top commenters.
>>>   * Activity of a user in a period(Measured by comments?)
>>>
>>> For reports similar to current reports functionality:
>>>   * Tickets opened/closed/assigned to a particular user in a specified
>>> period.
>>>   * Abandoned tickets - tickets that haven't been modified for a long
>>> time.
>>>   * x highest priority tickets that are closed during the current week.
>>>   * x highest priority tickets that still remain open .
>>>
>>> Or similar variations of these can be added while doing the project. I am
>>> not sure if "all" of these will be really useful for an issue tracker. So
>>> if you feel anything is unnecessary, please reply.
>>>
>>> [1] http://trac-hacks.org/wiki/**TracTicketStatsPlugin<http://trac-hacks.org/wiki/TracTicketStatsPlugin>
>>>
>>> PS: I will be using the same in my application. So if you feel any part
>>> is
>>> not clear, please specify. Thanks :)
>>>
>>> Regards,
>>> Shiva Teja
>>>
>>>
>> Hi,
>>
>> Are you saying that you propose to write a set of reports within the
>> existing report framework?
>>
>> Cheers,
>>     Gary
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message