Modify ↓
#15 closed task (fixed)
Milestone Handling
Reported by: | Garrett McGrath <gmcgrath@…> | Owned by: | bas |
---|---|---|---|
Priority: | critical | Milestone: | |
Component: | email2trac | Version: | 0.9.5 |
Keywords: | <Default> | Cc: | <Default> |
Description
To whom it may concern: I'm looking at modifying the email2trac script to enable it to handle a 'category' flag. Specifically we are using Trac as a data portal for our users and are exploring using the ticket system to track help requests to make life easier for our users (quick referrence to past issues and etc.). I'm thinking that the milestones system would be an easy way to segregate our emailed tickets automatically. eg. if we get a feature request for our calendar that goes to 1 email, and general help to a second email address, these simply populate the same ticket system in trac but with different milestones attached to them (or components as that would be nice to split things up with as well). So my question is has anyone does this before, and do I just need to modify the email2trac.py program or do the .c and .h files get modified as well. -Garrett McGrath
Attachments (2)
Change History (8)
Changed 16 years ago by Garrett McGrath
comment:3 Changed 16 years ago by anonymous
- Owner changed from bas to anonymous
- Status changed from new to assigned
Garrett,
I have read your email but i don't understand what you want to accomplish. Do you want to duplicate tickets or do you just want to set the milestone field of ticket to a default value? You can already set the default component in email2trac on the command line.
Regards
comment:4 Changed 16 years ago by bas
- Owner changed from anonymous to bas
- Status changed from assigned to new
comment:5 Changed 16 years ago by Garrett McGrath
Actually I think the 'component' flag that you can deliver to the script will allow me to do what I need to do. Basically we want different email address to populate tickets for different components so that they are serviced by different people. The components in this case are gonna be actually different systems we service as this is a data portal and not actually a project components. -Garrett email2trac wrote: > #15: Milestone Handling > -----------------------------------------------------+-------------- -------- > Reporter: Garrett McGrath <gmcgrath@Princeton.EDU> | Owner: anonymous > Type: defect | Status: assigned > Priority: major | Component: email2trac > Version: 0.9.5 | Resolution: > Keywords: | > -----------------------------------------------------+-------------- -------- > Changes (by anonymous): > > * status: new => assigned > * owner: bas => anonymous > > Comment: > > Garrett, > > > I have read your email but i don't understand what you want to > accomplish. Do you want to duplicate tickets or do you just want to set > the milestone field of ticket to a default value? You can already set the > default component in email2trac on the command line. > > > > > > Regards > >
comment:6 Changed 16 years ago by bas
- Resolution set to fixed
- Status changed from new to closed
comment:7 Changed 16 years ago by anonymous
- Cc <Default> added
- Keywords <Default> added
- Priority changed from major to critical
- Type changed from defect to task
Note: See
TracTickets for help on using
tickets.
Added by email2trac