DITrack in our company

[Vlad Skvortsov]

Andrey,

haven't heard anything back from you regarding this email. Can you 
comment if still interested please?


Vlad Skvortsov wrote:
> Andrey Ignatov wrote:
>
> [skipped]
>
>   
>>>> As for the future expectations.
>>>> We'd like to see the following in DITrack :
>>>> - the "assign" item by creating an issue
>>>>  
>>>>       
>>>>         
>>> I think it's i#50.
>>>     
>>>       
>> Yes, apparently it's i#50. We are looking forward to the version where it'll 
>> be implemented.
>>   
>>     
>
> It's currently slated for 0.7.
>
>   
>>>> - the "dt ls" ability to filter issues by the creation / modification 
>>>> time
>>>>  
>>>>       
>>>>         
>>> Like "older than 3 days"? Or "opened within last 8 hours"? Or what?
>>>     
>>>       
>> Yes, you are right. We run 24 hour administration and every morning I'd like 
>> to see what changes occur in DITrack tasks database for the last 24 hours 
>> i.e. who closed the tasks and what tasks were closed, who added comments 
>> etc.
>> It would be very convenient to have something like:
>>
>> dt ls lastday
>> dt ls lastweek
>>
>> etc.
>>
>> where lastday, lastweek etc. are time frame filters which i set.
>>   
>>     
>
> So basically you need to see what comments where added within specified 
> timeframe, which is very similar in spirit to issuing "svn log 
> -r{yesterday} -r{now} issues". Is that right?
>
> Also we have to keep in mind that the primary purpose of the 'list' 
> command is to list issue ids. Will you be satisfied to get a list of 
> issues in the response to your query? E.g. you'll still need to wander 
> through that list to figure out what was actually changed.
>
> Maybe we should implement something close to 'svn log', returning a list 
> of changes (i.e. comment ids possibly along with textual descriptions) 
> made within a given timeframe?
>
>
>   
>>>> - the "dt ls" ability to set list of fields for displaying - for
>>>> example, the category of the issue is more important to us than its version
>>>>  
>>>>       
>>>>         
>>> i#20?
>>>     
>>>       
>> Yes, it is. Looking forward to its implementation.
>>   
>>     
>
> Also slated for 0.7.
>
>
>   
>>>> - easy-to-use notification system (when a new issue or comment is added)
>>>>  
>>>>       
>>>>         
>>> i#64? What exactly do you need to be notified of? How would it be 
>>> different from the current commit emails?
>>>     
>>>       
>> We'd like to be notified of all actions carried out with tasks, e.g. task 
>> adding, commenting on tasks, change of version, assign of task to the user, 
>> task closing.
>>   
>>     
>
> Here is a snippet of a commit email which was generated by the current 
> version of DITrack (to be released as 0.6):
>
> =====
>
> Author: vss
> Date: 2007-06-15 13:11:57 -0700 (Fri, 15 Jun 2007)
> New Revision: 1658
>
> Added:
>    issues/data/i142/comment2
> Log:
> i#142: link rXXX to ViewCVS
>  * reopened
>
> In here:
>
> http://issues.ditrack.org/index.cgi?issue=114#c8
>
> ...the following text snippet is not hyperlinked:
>
> "r1477: Changed comment output format (quotes before and after comment were deleted). Also changed tests."
>
> (diff goes here)
> ======
>
> Will this kind of message satisfy your needs? It does contain a list of changes ("reopened") and the comment text.
>
>
>   
>> Basically we are satisfied with the svn-hook we are currently using. The 
>> only thing which causes some inconvenience is issue diff which has place in 
>> the emails from svn, accordingly emails include such lines as
>>
>> --- issues/data/i139/comment1                           (rev 0)
>> +++ issues/data/i139/comment1   2007-06-06 07:53:46 UTC (rev 478)
>>
>> or pluses at the beginning of added lines.
>>
>> We would like only important information to be included in letters.  May be 
>> when I have time I'll make the svn-hook, which i currently use, better but i 
>> think DITrack team may do it sooner and in high-quality manner.
>>   
>>     
>
> So, leaving alone the diff itself for now, anything else you'd like to 
> see changed in the message?
>
>   
>> As for i#64 I do not completely understand what would you like to do here? 
>> Are you talking about svn-hook working on svn-server or about some tool that 
>> will work at the same place where WC is stored?
>>   
>>     
>
> Basically there will be a DITrack client application  ("announcer"), run 
> under headless account, with its own (read-only) WC. The application 
> will periodically update its WC and send out emails summarizing the 
> changes happened. There will be an option to customize emails, filter 
> what changes are announced and who receives the emails.
>
>   


-- 
Vlad Skvortsov, vss at 73rus.com, http://vss.73rus.com