[Trac] Report dates
Hi all, I have 2 related questions: 1) I am trying to write a report that will show all tickets with changetime smaller than a given date. For example: 1/1/2009. My report works fine, besides the date part. I have tried writing the following: changedate = '2009-01-01' in all sort of way with no luck. How can I make date comparisons work in Trac reports? 2) I want the date (from part 1) to be a dynamic parameter to the report. As far as I understand this can be done by doing something like: $MY_DATE. But I want this date to be some system variable that will be auto-calculated. Actually this date should be the last date of the build put in Test (QA) environment. This way I want to be able to show all closed tickets that are already in Test environment. I have the date value of the last build in some text file. Is there a way of reading the last build date from a text file and sending it as a parameter to the report? Thanks in advance. Guy. --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Roadmap iCalendar, Lightning and basic auth problem
Quoting Noah Kantrowitz n...@coderanger.net: HTTPAuth plugin can handle this. You will need to add ics to the list of formats that require auth in trac.ini. Thanks, I will try it. Is the plugin OK for 0.11? The description on trac-hacks.org and the directory structure suggests that it is for 0.10 only. --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] HTTPAuth problem
Hi, I am trying the HTTPAuth plugin with trac 0.11.1, but I'm not sure how to configure it. Currently my username/password are not accepted. In trac.ini I added the fields as documented in http://trac-hacks.org/wiki/HttpAuthPlugin#Example [account-manager] password_file = /var/lib/trac/myproject/.htpasswd password_format = htpasswd [components] acct_mgr.* = enabled acct_mgr.admin.accountmanageradminpage = enabled acct_mgr.api.accountmanager = enabled acct_mgr.htfile.abstractpasswordfilestore = enabled acct_mgr.htfile.htpasswdstore = enabled acct_mgr.web_ui.accountmodule = enabled acct_mgr.web_ui.loginmodule = enabled acct_mgr.web_ui.registrationmodule = disabled customfieldadmin.api.* = enabled customfieldadmin.customfieldadmin.* = enabled trac.web.auth.loginmodule = disabled httpauth.* = enabled [httpauth] paths = /xmlrpc, /login/xmlrpc, /roadmap I also applied this patch: http://trac-hacks.org/attachment/ticket/3100/authenticated.patch But for the roadmap page the web browser asks for my password, even if I'm already logged in and does not accept it. I tried multiple times to be sure, that I typed the right password. I use Apache 2.2.9 with AuthType Basic, Require valid-user, HTTPS. Thanks in advance for any useful hint! --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: hide fields that don't apply during ticket entry
On Thu, Jan 15, 2009 at 02:56:55PM -0800, jevans wrote: Hello, We're setting up a project with both internal and external access using Trac 0.11.2.1. We're using the BlackMagicTicketTweaks plug-in to restrict some internal fields based on permissions. But we would also like to hide other fields during ticket entry that just don't apply until later in the process. It's not that the reporter shouldn't ever see them, just that they don't apply to ticket creation. I thought the TIcketSubmitPolicy plug-in would do this but it doesn't seem to handle checking the status field. Ticketed, http://trac-hacks.org/ticket/4487 I can't promise I'll get to it anytime soon, however. Jeff Hammel IRC: jhammel, k0s --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Tracd don't load anything but it seems to work fine on shell
Hi finally I was able to backup/restore our current Trac project into new Trac environment on Centos 5. Thanks to Emmanuel by his help :) Bye On 17 ene, 14:46, Emmanuel Blot manu.b...@gmail.com wrote: Unfortuneatly, I haven't much experience with TRAC. I mounted TRAC with Tracd one year ago but I don't really understand how TRAC works. Can you guide me a little? Re-read the documentation. It is not perfect, but it'll give you the basic commands and options. tracd is the standalone web server, trac-admin is the command-line administration tool that help configuring and performing maintenance tasks. run trac-admin /path/to/one/of/your/trac/project and see if you can obtain the list of permissions for example (type help to get the list of available command at the trac-admin prompt) --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Backup and Restore on a new Centos 5 installation
Done with Trac Wiki Backup guide. Bye On 16 ene, 18:08, Ruben O rubeno...@yahoo.es wrote: Hi few days ago I posted here to get help about a Tracd problem. Meanwhile I wait some help of gurus of Trac(thanks to Emmanuel Blot), Im goint to mount a new installation of Trac with latest version. So my main doubt is What things of currently Trac environment I have tobackup? We are using Trac and subversion ( I don't know If database backend is sqlite or mysql Oo). So I need to do abackupof our unique project on this Trac environement and after restore on the new installation? - Do you recommended this idea? - How can I list projects on curren Trac with trac-admin? Thanks guys PD1: I always used this command to run tracd: tracd -p 8080 --auth=trac,/var/lib/trac/trac/conf/users-digest,realm / var/lib/trac/trac Have I to understand that our project is in /var/lib/trac/trac ? Because I try to init with trac-admin and returned Initenv for '/var/lib/trac/trac' failed. Does an environment already exist? --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: hide fields that don't apply during ticket entry
On Tue, Jan 20, 2009 at 09:52:51AM -0500, Jeff Hammel wrote: On Thu, Jan 15, 2009 at 02:56:55PM -0800, jevans wrote: Hello, We're setting up a project with both internal and external access using Trac 0.11.2.1. We're using the BlackMagicTicketTweaks plug-in to restrict some internal fields based on permissions. But we would also like to hide other fields during ticket entry that just don't apply until later in the process. It's not that the reporter shouldn't ever see them, just that they don't apply to ticket creation. I thought the TIcketSubmitPolicy plug-in would do this but it doesn't seem to handle checking the status field. Ticketed, http://trac-hacks.org/ticket/4487 I can't promise I'll get to it anytime soon, however. OOps, you beat me to it! #4463 Jeff Hammel IRC: jhammel, k0s --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Difference between user login and internal Trac user?
Hi I continue with my efforts to understand a little bit Trac environment. Recently I restored old Trac project to new Centos 5 installation. On 0.11 version, I noticed that Admin Plugin is not necessary because is on package by default. I don't understand something(well, I don't understand a lot of things :p): To login to TRAC, you need to add a user through httpasswd -m /path/to/ proyect username and combinating Apache setup, you can ... ask for a password with directive AuthUserFile /srv/trac/project.htpasswd. But Trac have a DB users on SQLite, the users who really have permissions to do somehting on TRAC, so the users of Apache(when you login to trac) and users of DB SQLite are not the same, aren't they? I think is a confusing topic, but Im very newbie with TRAC. Because to add a normal user to Trac, first you need to add user and password through htpasswd and later create the same user in Trac(the user is created then on DB with permissions). Sorry by newbie questions. Thanks! --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Difference between user login and internal Trac user?
But Trac have a DB users on SQLite, the users who really have permissions to do somehting on TRAC, so the users of Apache(when you login to trac) and users of DB SQLite are not the same, aren't they? It is probably written somewhere in the docs, anyway to sum up: 1/ Apache is in charge of managing user *authentication*: whether the user exists on the system, and whether its credentials can be validated against a authentication backend (whichever it is: htpasswd, LDAP, SSPI, etc.) 2/ Trac is in charge of managing user *permissions*: whether user 'U' can perforn operation 'O' on Trac. It is not an M-M mapping: Trac defines two special groups (namely anonymous and authenticated user groups), and allows to define any other group of users to grant permissions for groups in addition to per-user permissions. Trac is not involved in authenticating users at all when you use Apache as the web server. Cheers, Manu --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Difference between user login and internal Trac user?
On Tue, Jan 20, 2009 at 11:34 AM, Ruben O rubeno...@yahoo.es wrote: Hi Hello ... I don't understand a lot of things :p): ... well ... that happens to me too ... the only thing I am really sure about is that Trac is great ... :P ... To login to TRAC, you need to add a user through httpasswd -m /path/to/ proyect username and combinating Apache setup, you can ... ask for a password with directive AuthUserFile /srv/trac/project.htpasswd. Security can be seen from different perspectives ... first you have user login methods (e.g. Basic/Digest Auth, ...), next you have user credentials (e.g. httpasswd, MS AD, LDAP, Local Windows Accounts, ...), next you have permissions and authorization (e.g. TRAC_ADMIN, WIKI_MODIFY ... and maybe even OAuth ;), and so on ... e.g. user groups, etc ... It is also possible to see in practice further layers (e.g. CoSign ;) But Trac have a DB users on SQLite, the users who really have permissions to do somehting on TRAC, so the users of Apache(when you login to trac) and users of DB SQLite are not the same, aren't they? Trac separates these concepts. There should be a login module to handle user login. There are AuthStores to validate user credentials. This process may be handled by Trac itself ... but could also be delegated to the web-server hosting the Trac instance using the WSGI standard library REMOTE_USER (... AFAICR ...). this kind of auth delegation, for example, makes Trac integration with CoSign filters relatively smooth ... since there is a very well established separation of concerns, and a standard way to communicate user ids. BTW ... there are permissions (i.e. PermissionSystem ...) ... which are defined on a per-user/group basis. In this case Trac stores user permissions in the env's database, since their semantics (meaning ...) is quite related with the core services and those provided by extensions (e.g. XMLRPC ...). Nonetheless group membership and so on can be retrieved from elsewhere (e.g. LDAP dir ;). The connection between these two sub-systems is given by the user names in Trac's DB matching the value assigned at run-time to the REMOTE_USER variable (which is set by the auth provider ... i.e. an specific Trac component or third-party apps, let's say web servers ...). This means that Trac implementation is not strongly coupled to any security infrastructure you could ever imagine ... Conclusions ... Trac is great ! ... ;) I think is a confusing topic, Ooops ... are computer scientist the masters of chaos ? :) but Im very newbie with TRAC. Hope you have learned a little bit ... ;) Moreover there should be at least some other references about this particular subject. I mean something about WSGI security architecture ... Because to add a normal user to Trac, first you need to add user and password through htpasswd and later create the same user in Trac(the user is created then on DB with permissions). This is not compulsory ... you could do any of them any time, you could even migrate your server and have no (or an empty ;) auth store but user permissions will be there ... Sorry by newbie questions. The best way to learn is to ask ... :) -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] TicketDep Plugin for MasterTicketsPlugin installation question
The MasterTicketsPlugin page (http://trac-hacks.org/wiki/ MasterTicketsPlugin) now references a TicketDepPlugin (http://trac- hacks.org/wiki/TicketDepPlugin) See http://groups.google.com/group/trac-dev/browse_thread/thread/7d8d1a2032f068e8?hl=en# for more information about A Christmas gift - TicketDep plugin TicketDepPlugin visualises Blocking and Blocked by relations of the MasterTicketsPlugin by showing tickets in nested tables. The screen images on the page and the flexible settings look very good. I have the MasterTicketsPlugin running and have some issues with Blocking and Blocked by values. I have installed the TracTicketDep-0.11_20081224-py2.4.egg file in our Trac environment's plugins directory but I have not been able to get it to run. Do I need to add entries in the trac.ini components lists? I tried adding: tracticketdep.* = enabled and ticketdep.* = enabled I stopped and started our apache2 server but nothing appears. It also does not show in the Trac Admin screen when showing plugins. Here is our System Information from About Trac Trac: 0.11.2 Python: 2.5.1 (r251:54863, Sep 21 2007, 22:46:31) [GCC 4.2.1 (SUSE Linux)] setuptools: 0.6c8 MySQL: server: 5.0.67-community, client: 5.0.67, thread-safe: 0 MySQLdb:1.2.2 Genshi: 0.5.1 mod_python: 3.3.1 Subversion: 1.5.5 (r34862) jQuery: 1.2.6 Thanks in advance for any suggestions. --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: TicketDep Plugin for MasterTicketsPlugin installation question
Grr, I really wish people would stop finding that plugin. Egg files are tagged to a single version of Python. Try renaming it to be py2.5 instead of py2.4. If the author is out there in cyberspace somewhere, please fix your downloads and actually post the source instead of a single version of the egg. --Noah -Original Message- From: trac-users@googlegroups.com [mailto:trac-us...@googlegroups.com] On Behalf Of gctrekker Sent: Tuesday, January 20, 2009 11:15 AM To: Trac Users Subject: [Trac] TicketDep Plugin for MasterTicketsPlugin installation question The MasterTicketsPlugin page (http://trac-hacks.org/wiki/ MasterTicketsPlugin) now references a TicketDepPlugin (http://trac- hacks.org/wiki/TicketDepPlugin) See http://groups.google.com/group/trac- dev/browse_thread/thread/7d8d1a2032f068e8?hl=en# for more information about A Christmas gift - TicketDep plugin TicketDepPlugin visualises Blocking and Blocked by relations of the MasterTicketsPlugin by showing tickets in nested tables. The screen images on the page and the flexible settings look very good. I have the MasterTicketsPlugin running and have some issues with Blocking and Blocked by values. I have installed the TracTicketDep-0.11_20081224-py2.4.egg file in our Trac environment's plugins directory but I have not been able to get it to run. Do I need to add entries in the trac.ini components lists? I tried adding: tracticketdep.* = enabled and ticketdep.* = enabled I stopped and started our apache2 server but nothing appears. It also does not show in the Trac Admin screen when showing plugins. Here is our System Information from About Trac Trac: 0.11.2 Python: 2.5.1 (r251:54863, Sep 21 2007, 22:46:31) [GCC 4.2.1 (SUSE Linux)] setuptools: 0.6c8 MySQL:server: 5.0.67-community, client: 5.0.67, thread-safe: 0 MySQLdb: 1.2.2 Genshi: 0.5.1 mod_python: 3.3.1 Subversion: 1.5.5 (r34862) jQuery: 1.2.6 Thanks in advance for any suggestions. --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] filter own TRAC bug mail
Gentlemen, the TRAC bug tracker is not as smart as bugzilla. It insists on sending one acknowledgements even for one's own actions. It was me doing the clicking, no acknowledgement needed. But if it was someone else changing/commenting on one of my bugs, well yes, I want mail about it. So to get mail on others' actions on our bugs, but not our own actions, we must make fancy SpamAssassin rules: header __J_TRAC_COMMENT X-Trac-Ticket-URL =~/\#comment/ rawbody __J_TRAC_MY_COMMENT /\+-+\nChanges \(by jidanni\):\n/ meta J_TRAC_OTHERS __J_TRAC_COMMENT !__J_TRAC_MY_COMMENT score J_TRAC_OTHERS -7 Fortunately TRAC breaks other rules, like missing To: headers, so the above is all I need, at least for the WordPress TRAC. --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Download in other formats link not available
I'm running Trac 0.11. There is not a Download in other formats link at the bottom of the code browser window. Anyone else seen this and know how to fix it? --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: filter own TRAC bug mail
Fortunately TRAC breaks other rules, like missing To: headers, so the above is all I need, at least for the WordPress TRAC. Trac does emit To: headers, it depends on the notification configuration. I agree that the notification documentation is weak and that notification features are too far limited, but I don't see how not emitting To: header can be considered as breaking a rule. --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: filter own TRAC bug mail
To be fair, I often want trac to send me acknowledgements as I use email for organization (maybe not the best decision, but that's what I do). Though there's no reason the notification to be mandatory except as a policy decision. Jeff Hammel IRC: jhammel, k0s On Wed, Jan 21, 2009 at 02:51:56AM +0800, jida...@jidanni.org wrote: Gentlemen, the TRAC bug tracker is not as smart as bugzilla. It insists on sending one acknowledgements even for one's own actions. It was me doing the clicking, no acknowledgement needed. But if it was someone else changing/commenting on one of my bugs, well yes, I want mail about it. So to get mail on others' actions on our bugs, but not our own actions, we must make fancy SpamAssassin rules: header __J_TRAC_COMMENT X-Trac-Ticket-URL =~/\#comment/ rawbody __J_TRAC_MY_COMMENT /\+-+\nChanges \(by jidanni\):\n/ meta J_TRAC_OTHERS __J_TRAC_COMMENT !__J_TRAC_MY_COMMENT score J_TRAC_OTHERS -7 Fortunately TRAC breaks other rules, like missing To: headers, so the above is all I need, at least for the WordPress TRAC. --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: filter own TRAC bug mail
On Jan 20, 12:51 pm, jida...@jidanni.org wrote: Gentlemen, the TRAC bug tracker is not as smart as bugzilla. It insists on sending one acknowledgements even for one's own actions. It was me doing the clicking, no acknowledgement needed. But if it was someone else changing/commenting on one of my bugs, well yes, I want mail about it. So to get mail on others' actions on our bugs, but not our own actions, we must make fancy SpamAssassin rules: header __J_TRAC_COMMENT X-Trac-Ticket-URL =~/\#comment/ rawbody __J_TRAC_MY_COMMENT /\+-+\nChanges \(by jidanni\):\n/ meta J_TRAC_OTHERS __J_TRAC_COMMENT !__J_TRAC_MY_COMMENT score J_TRAC_OTHERS -7 Fortunately TRAC breaks other rules, like missing To: headers, so the above is all I need, at least for the WordPress TRAC. Actually, it's significantly smarter/better than Bugzilla. Particularly out of the box. That said, your assumption that $USER who edits a ticket shouldn't get a notification is a personal preference, and by extension a flawed assumption. I personally expect to get an e-mail in this scenario. Enjoy Bugzilla, sounds like the tool of choice for you. --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: filter own TRAC bug mail
Look at http://trac-hacks.org/wiki/NeverNotifyUpdaterPlugin It works for us. Search this group for nevernotifyupdaterplugin and you will see two posts I made on 12/5/2008 with more details. On Jan 20, 5:02 pm, Jeff Hammel jham...@openplans.org wrote: To be fair, I often want trac to send me acknowledgements as I use email for organization (maybe not the best decision, but that's what I do). Though there's no reason the notification to be mandatory except as a policy decision. Jeff Hammel IRC: jhammel, k0s On Wed, Jan 21, 2009 at 02:51:56AM +0800, jida...@jidanni.org wrote: Gentlemen, the TRAC bug tracker is not as smart as bugzilla. It insists on sending one acknowledgements even for one's own actions. It was me doing the clicking, no acknowledgement needed. But if it was someone else changing/commenting on one of my bugs, well yes, I want mail about it. So to get mail on others' actions on our bugs, but not our own actions, we must make fancy SpamAssassin rules: header __J_TRAC_COMMENT X-Trac-Ticket-URL =~/\#comment/ rawbody __J_TRAC_MY_COMMENT /\+-+\nChanges \(by jidanni\):\n/ meta J_TRAC_OTHERS __J_TRAC_COMMENT !__J_TRAC_MY_COMMENT score J_TRAC_OTHERS -7 Fortunately TRAC breaks other rules, like missing To: headers, so the above is all I need, at least for the WordPress TRAC. --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Creating Custom Ticket Status
On Jan 19, 8:58 pm, bardy bard...@gmail.com wrote: 2009/1/20 yoh...@gmail.com: but yes, it can certainly be done. can you create a ticket which is not the default status new but a custom status , say myNew ? Yes, however you might need to leverage a plugin in two. Such as the TicketCreationStatus plugin, etc. Others probably can provide more helpful insight, I have also had all new tickets be New, personally. It fits with our work flow requirements. You might also want to look at the PrivateTickets plugin and the SupportTickets plugin as it sounds like these might apply to your usage. The ClientsPlugin (or similar) may also be relevant. --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: filter own TRAC bug mail
I see, http://trac-hacks.org/wiki/NeverNotifyUpdaterPlugin is something one must ask each trac maintainer to install, at each trac where we have reported bugs. I will rather just filter the mail myself with my SpamAssassin stanza version 2: header __J_TRAC_COMMENT X-Trac-Ticket-URL =~/\#comment/ rawbody __J_TRAC_MY_COMMENT /\+-+\n(Changes|Comment) \(by jidanni\):\n/m meta J_TRAC_OTHERS __J_TRAC_COMMENT ! __J_TRAC_MY_COMMENT score J_TRAC_OTHERS -7 Missing To: headers at the trac I used upped SpamAssassin's score so I didn't need up their threshold to filter. I hope one day vanilla Trac will offer more than all or none email choices. --~--~-~--~~~---~--~~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
