[Trac] Re: Announce new version of email2trac (version 0.8.2)

2006-10-30 Thread Bas van der Vlies

Gary Oberbrunner wrote:
 Bas van der Vlies wrote:
   Yes there is a convention. When i ticket is inserted it gets a  
 tickets id, eg #4
 This number is inserted in the description field of ticket. This is  
 the same as the subject line
 for emails (notifications). If you hit reply and update_ticket is set  
 and #4 is not removed from the subject line it will
 try to update the ticket.
 
 Thanks, I see.  It must have a regex matching the subject against something
 like '\b#[0-9]+\b'.  That makes sense.  And then how does it actually update
 the ticket (change status, etc.)?  Is that done by similar special regexes in
 the body, kind of like how the trac post-commit hook works?


Garry,

  I only support updates for comments. The other stuff like ticket 
closing and changing status is not implemented.

Regards
-- 
--

*  *
*  Bas van der Vlies e-mail: [EMAIL PROTECTED]  *
*  SARA - Academic Computing Servicesphone:  +31 20 592 8012   *
*  Kruislaan 415 fax:+31 20 6683167*
*  1098 SJ Amsterdam   *
*  *


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Trac 
Users group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/trac-users
-~--~~~~--~~--~--~---



[Trac] Re: Announce new version of email2trac (version 0.8.2)

2006-10-28 Thread Malcolm J Harwood

On Friday 27 October 2006 11:51, Bas van der Vlies wrote:

 If you hit reply and update_ticket is set and #4 is not removed from the
 subject line it will try to update the ticket.

Is there a way to get it to trim what it inserts into the ticket? At work we 
have folks who insist on top-posting and never trim their replies, so the 
entire history of the ticket ends up in each comment. 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Trac 
Users group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/trac-users
-~--~~~~--~~--~--~---



[Trac] Re: Announce new version of email2trac (version 0.8.2)

2006-10-27 Thread Gary Oberbrunner

Bas van der Vlies wrote:
- Fixed an error in Ticket Update. When ticket
does not exists, proceed as if it is a new ticket

I may be interested in this plugin, but I don't see in the documentation how
emails are mapped to existing tickets, and what fields in the email are used
to update the ticket (change status, take, etc.).  There must be certain
conventions used, yes?

-- Gary Oberbrunner

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Trac 
Users group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/trac-users
-~--~~~~--~~--~--~---



[Trac] Re: Announce new version of email2trac (version 0.8.2)

2006-10-27 Thread Rainer Sokoll

On Fri, Oct 27, 2006 at 11:04:24AM -0400, Gary Oberbrunner wrote:
 
 Bas van der Vlies wrote:
 - Fixed an error in Ticket Update. When ticket
 does not exists, proceed as if it is a new ticket
 
 I may be interested in this plugin, but I don't see in the documentation how
 emails are mapped to existing tickets, and what fields in the email are used
 to update the ticket (change status, take, etc.).

Documentation is in email2trac itself:

8---
The scripts reads emails from stdin and inserts directly into a Trac
database.
MIME headers are mapped as follows:

* From:  = Reporter
 = CC (Optional via reply_address option)
* Subject:   = Summary
* Body   = Description
* Component  = Can be set to SPAM via spam_level option
8---

Rainer


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Trac 
Users group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/trac-users
-~--~~~~--~~--~--~---



[Trac] Re: Announce new version of email2trac (version 0.8.2)

2006-10-27 Thread Gary Oberbrunner

Bas van der Vlies wrote:
   Yes there is a convention. When i ticket is inserted it gets a  
 tickets id, eg #4
 This number is inserted in the description field of ticket. This is  
 the same as the subject line
 for emails (notifications). If you hit reply and update_ticket is set  
 and #4 is not removed from the subject line it will
 try to update the ticket.

Thanks, I see.  It must have a regex matching the subject against something
like '\b#[0-9]+\b'.  That makes sense.  And then how does it actually update
the ticket (change status, etc.)?  Is that done by similar special regexes in
the body, kind of like how the trac post-commit hook works?

thanks!

-- Gary

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Trac 
Users group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/trac-users
-~--~~~~--~~--~--~---