[Trac] Re: Inserting a hook in ticket creation
On Fri, Oct 17, 2008 at 11:33 AM, Sachin Arora <[EMAIL PROTECTED]> wrote: > Culapov - > > Thanks for the tip, appreciate it. > > Could you also tell me what change would I need to make to ensure that my > new class gets picked up by Trac Installation, rather than the default one > you mentione below? > For this class to be picked up by trac and to be used you have to create a trac plugin with it or to put the py file in the plugins directory of you trac environment. Also you have to enable this new trac component(python class) from the trac.ini file. Read this page for more details on trac plugins http://trac.edgewall.org/wiki/TracPlugins and details about how to develop plugins http://trac.edgewall.org/wiki/TracDev/PluginDevelopment --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Inserting a hook in ticket creation
On Fri, Oct 17, 2008 at 1:20 AM, Sachin Arora <[EMAIL PROTECTED]> wrote: > > Hi all - > > I am new to Trac. So thought of asking help from the experts on this > group. > > I am in a situation where I need to do some processing of my own(hit > an URL and submit some data), after a new ticket is being saved. > you have to create a new class that implements an ITicketChangeListener and then overwrite the ticket_created method. You can see this class defined in http://trac.edgewall.org/browser/branches/0.11-stable/trac/ticket/api.py#L109 --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Adding "drill down" to reports
On Thu, Oct 9, 2008 at 6:00 PM, Chris Nelson <[EMAIL PROTECTED]> wrote: > > In the Road Map, you can click on a Milestone or its ticket counts to get > more information. It'd be really helpful if you could click on part of a > report (like a group header) and get to more detail. The most obvious way > (generating [report:24?USER=user] or as the group > header value) is escaped by Trac so that it shows up literally. If there > anyway I can add links to report? I created a plugin that does something like this. Take a look at http://code.optaros.com/trac/oforge/wiki/Dashboard. Take a look on the bottom of the page for some examples and for details look on the linked pages. --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Spacing around TicketQuery()
sorry but i gaved you the internal url, try http://code.optaros.com/trac/oforge/wiki/Dashboard --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Spacing around TicketQuery()
> But no matter where I've tried putting [[br]], I can't get a break after "No > results" that doesn't give an extra break when there are results. I just > want one line before each numbered item (headline). Any thoughts? > try this plugin https://projects.optaros.com/trac/oforge/wiki/Dashboard for a better UI. --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: features of TicketQuery
> > This is nice, no information on how to get it and install it though, > just a page of how it looks. > > Looks very nice btw. i added some nstall info on the wiki page http://code.optaros.com/trac/oforge/wiki/Dashboardpage --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: features of TicketQuery
> I think you mean: > > > http://code.optaros.com/trac/oforge/wiki/Dashboard > > right? > right --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: features of TicketQuery
On Fri, Jul 25, 2008 at 3:11 PM, Emin <[EMAIL PROTECTED]> wrote: > > Dear Experts, > > The TicketQuery macro is really wonderful, so wonderful that I use it > a lot and would like to ask about more features. Is there a way to > control the order of the results? add in the parameters list sort=ticket_field For example, if I want to sort by > date or by reverse ticket id or by user, is there a way to do that? > > Also, since TicketQuery is called a macro, this suggests that there is > some source code for it that calls internals of Trac. Is there a way > for users to add such macros? If so, could someone point me to the > source code of TicketQuery and how I would write a version with more > features? > The TicketQuery code you can find it in trac.ticket.query module. For creating a macro take a look at http://trac.edgewall.org/wiki/WikiMacros I created a plugin that does something similar to TicketQuery and that defines 3 new macros. The macros show counts of tickets based on a query string. You can take a look on http://code.optaros.com/trac/oforge/wiki/Dashboard page for more information on 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Rif: [Trac] Re: post-commit problem
On Fri, Jul 25, 2008 at 10:01 AM, <[EMAIL PROTECTED]> wrote: > > Hi all, some news. > I tried with another server, just to avoid messing up the two production > server. The new server is Ubuntu 2.6.22-14, while the other two are Fedora. > Aside from the different installation directories I think nothing should > change. > > Anyway here what I found: > > sudo -u www-data env -i ./post-commit > post-commit called. when you run the "sudo -u www-data env -i ./post-commit" command in the console the following things happen: 1. sudo changes the current user to www-data 2. opens the www-data console shell with a empty env 3. runs ./post-commit command in the new shell. If you take a look in the svn documentation for hooks you will see that svn server, when it calls a hook, passes some arguments. In the case of the post-commit hook it passes the path to the svn repository(REPOS variable in your sh script) and the revision that triggered the call(REV in your sh script). So you have to provide in your command this information. This note that i'm making it wount solve your problem, because the svn server at commit time passes the parameters, but it will help you find out what goes wrong. > > The content of the post-commit file is. > #!/bin/sh > > # POST-COMMIT HOOK > # > # . > # . > # . > # some comments here > # . > # . > # . > > REPOS="$1" > REV="$2" > > echo "post-commit called." > echo "$REPOS" > /var/lib/svn//hooks/rep.txt > > The file properties are: > > -rwxrwxrwx 1 www-data root 1979 2008-07-24 10:47 post-commit > > So it seem that it works. But, as before, it is not called after a commit to > the above repository (neither I see anything on the shell nor the file > rep.txtis created). > > Do I forget or overlook something ? > Am I wrong supposing that the file post commit should be executed after a > successful commit ? the post-commit is always called after a successful commit. --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Trac / Subversion / IDE integration
On Tue, Jul 8, 2008 at 4:25 PM, svaens <[EMAIL PROTECTED]> wrote: > > Hi guys, > > I am new to Trac, and am really still evaluating it. Trying to decide > whether to upgrade to modern versions of bugzilla (we've got a version > 3 years old or so) or give Trac a go. Personally, from what i've seen > of bugzilla it is not that user friendly, so I am open to change. But > at the same time I have used other Issue tracking tools and miss the > functionality of those. I would like to know if Trac can provide this > functionality. > > I used to use Fogbugz at my old place of work. With this, via a plugin > which integrated our version control system with the issue tracking > system (fogbugz), we could, when checking in a code change, specify an > Issue/bug number. > This meant that anyone browsing through the history of a bug (in > fogbugz) could see a list of modified files (shown as hyperlinks), and > when clicking on these hyperlinks, is shown a diff of the previous > version, and checked in version, and so is shown exactly what changes > were made. you can try a plugin that was build on the trac-commit-hook to create that functionality. Also you will have a administration panel in trac to enable more options. http://code.optaros.com/trac/oforge/wiki/SVNPoliciesPlugin --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Ticketworkflow
Hi Jani, I implemented a workflow controller(WorkflowControllerPlugin) that does exactly what you need and more. This workflow controller must be used with another plugin (UserManagerPlugin) that defines roles and that manages users. For more information please take a look at the wiki page that describes this plugin. http://code.optaros.com/trac/oforge/wiki/WorkflowControllerPlugin. If you have questions or you want to set it up send me an email. On Thu, Jul 3, 2008 at 11:07 AM, Jani Tiainen <[EMAIL PROTECTED]> wrote: > > I suppose these are not possible in ticket workflow yet: > > Select set_owner from group. So I could define something like: > qa.set_owners = @tester and it would populate list of people having > group "tester". > > Also can I invent my own permissions for tickets like: > > qa.permission = TICKET_QA_MODIFY, PROJECT_MANAGER > > -- > Jani Tiainen > > > > --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: post commit hook script
imho you don't have set the PYTHON_PATH to the site-packages where trac is installed. On Thu, Jun 5, 2008 at 12:15 AM, rishoboy6 <[EMAIL PROTECTED]> wrote: > > I am trying to integrate subversion and trac. I am using the post > commit hook script found at > http://trac.edgewall.org/browser/branches/0.10-stable/contrib/trac-post-commit-hook > to be able to modify tickets and in my post-commit.tmpl in my svn i > have > > REPOS="$1" > REV="$2" > LOG=`C:\Program Files\Subversion\bin\svnlook log -r $REV $REPOS` > TRAC_ENV='c:\projects\trac' > TRAC_URL='http://localhost:8000/myproject2' > > C:\Python24 C:\projects\svn\hooks\trac-post-commit-hook -p "$TRAC_ENV" > -r "$REV" -m "$LOG" -s "$TRAC_URL" > > This is currently not working when i try to commit. the commit works > fine, but the ticket is not modified. Also when i try to run the > script in windows, i get an error at the line > > from trac.env import open_environment > > saying > > Traceback (most recent call last): > File "C:\projects\svn\hooks\trac-post-commit-hook.py", line 6, in ? >from trac.env import open_environment > ImportError: No module named trac.env > > Am i missing something obvious? It could be something very simple, i > am new to all of this. any help would be appreciated. > > > > --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Announce new version of email2trac (version 0.30)
Very good news. Thank you for the great work you are doing. I'll update to this version. On Wed, Jun 4, 2008 at 10:52 AM, Bas van der Vlies <[EMAIL PROTECTED]> wrote: > > 2008-05-30 >* Fixed debian control file. Package can be build on any platform > and > not only on i386 platforms: > > Author: Christian Iversen ci add sikkerhed dot org > Applied by: Bas van der Vlies > >* We now use the trac configuration parser routine > Author: andrei2102 add gmail dot com > Applied by: Bas van der Vlies > >* Added new command line option -n/--dry-run. This option only show > what commands will be executed. > Author: Bas van der Vlies > >* the default values for tickets can now also be set in > 'email2trac.conf'. So you can use different values when an email > is converted to a ticket. The ticket value is set to this rules > - email2trac.conf > - trac.ini > > email2trac.conf use same format as trac.ini, eg email2trac.conf: >[project] >default_component : test > > closes request #55, for more info see: > - https://subtrac.sara.nl/oss/email2trac/wiki/ > Email2tracConfiguration > > Requested by: greg dot deakyne at etapestry dot com > Implemented by: Bas van der Vlies > >* Fixed a bug in ticket_update. It failed when project did not have > ticket component field, closes bug #62 > Reported by: gernot dot hillier add siemens dot com > Fixed by: Bas van der Vlies > >* run_email2trac.c: > - can no longer segfault after a failed malloc. > - after set*id failure, you'll get a diagnostic (or at least > nonzero exit status) and it won't attempt the exec. > > Author: Jim Meyering jim add meyering dot net > Applied by: Bas van der Vlies > > * Made some approvements to spam function: > - If the he X-Spam-Score header is present, but has no value > email2trac will crash, closes #63 > > - Added config option which header field we must check > for determing if mail is Spam, eg: > - spam_header : X-Spam-Level (default: X-Spam-Score) > > Author: email2trac at bulk dot squeakyblue dot com > Applied by: Bas van der Vlies > >* black_list is now a configuration option and is used to deny > email addesses, default value is: MAILER-DAEMON@ > > Can specifiy more then one email adress seperated by ',', eg: > black_list : [EMAIL PROTECTED], [EMAIL PROTECTED] > > closes #39, #56 > > Author: Bas van der Vlies > >* if mailto_link + german umlaut problem is fixed, closes #60 > Reported by: alex at pirsig dot net > Fixed by: Bas van der Vlies > > > > = Info about the package > > https://subtrac.sara.nl/oss/email2trac > > the latest stable email2trac package is available from: > ftp://ftp.sara.nl/pub/outgoing/email2trac.tar.gz > > email2trac - utilities > -- > > This is a release of the SARA package email2trac that contains utilities > that we use to convert emails to trac tickets. The initial setup was > made > by Daniel Lundin from Edgewall Software. SARA has extend the initial > setup, > with the following extensions: > > - HTML messages > - Attachments > - Use commandline options > - Config file is used to control the behaviour of the email2trac >software > - Unicode support for special characters in the headers of an > email >message > - Ticket updates via mail > > Comments or Suggestions mail them to: >email2trac <[EMAIL PROTECTED]> > > http://www.sara.nl for more info about SARA. > > > -- > Bas van der Vlies > [EMAIL PROTECTED] > > > > > > > --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: TracSvnPoliciesPlugin problem
We designed this plugin to work with trac 0.11. For example the templates are all genshi. I don't think that it will work for trac 0.10.4 but you can give it a try. On Sun, Jun 1, 2008 at 12:15 AM, Brett <[EMAIL PROTECTED]> wrote: > > This is a side question, but is the TracSvnPoliciesPlugin only > compatible with Trac 0.11, or can I use it with 0.10.4? > > > Brett > > > > On May 31, 1:37 pm, "Culapov Andrei" <[EMAIL PROTECTED]> wrote: >> We made the plugin to work only with svn. So sorry, but no. >> >> On Fri, May 30, 2008 at 10:30 PM, rupert thurner >> >> <[EMAIL PROTECTED]> wrote: >> >> > could you tell if policiesplug would be possible in conjunction with >> > mercurial, andhttp://www.trac-hacks.org/wiki/HgTimelinePluginas >> > well? >> >> > rupert. >> >> > On May 22, 4:10 pm, Robert C Corsaro <[EMAIL PROTECTED]> wrote: >> >> >> On Wed, May 21, 2008 at 10:36 PM, Pablo Fabregat >> >> >> <[EMAIL PROTECTED]> wrote: >> >> >>> Hi all, >> >> >> >>> I managed to get this plugin installed and it throws no errors... but >> >> >> when i do a commit, whatever policy i put, nothing happens, it just >> >> >> commits, >> >> >> and i can tell that the hook's being executed (it's in >> >> >> /usr/bin/svn-hook) >> >> >> because i edited that script to throw an error and, it does... >> >> >>> i'm almost done with this! :O >> >> >> >>> any ideas ? >> >> >>> thanks in advance! >> >> >> We worked this out on IRC, but the solution was to copy the >> >> svnpolicies/bin/svn-hook to /usr/local/bin overwriting the setuptools >> >> wrapper script. I'm working on a fix. > > > --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: TracSvnPoliciesPlugin problem
We made the plugin to work only with svn. So sorry, but no. On Fri, May 30, 2008 at 10:30 PM, rupert thurner <[EMAIL PROTECTED]> wrote: > > could you tell if policiesplug would be possible in conjunction with > mercurial, and http://www.trac-hacks.org/wiki/HgTimelinePlugin as > well? > > rupert. > > On May 22, 4:10 pm, Robert C Corsaro <[EMAIL PROTECTED]> wrote: >> >> On Wed, May 21, 2008 at 10:36 PM, Pablo Fabregat >> >> <[EMAIL PROTECTED]> wrote: >> >>> Hi all, >> >> >>> I managed to get this plugin installed and it throws no errors... but >> >> when i do a commit, whatever policy i put, nothing happens, it just >> >> commits, >> >> and i can tell that the hook's being executed (it's in /usr/bin/svn-hook) >> >> because i edited that script to throw an error and, it does... >> >>> i'm almost done with this! :O >> >> >>> any ideas ? >> >>> thanks in advance! >> >> We worked this out on IRC, but the solution was to copy the >> svnpolicies/bin/svn-hook to /usr/local/bin overwriting the setuptools >> wrapper script. I'm working on a fix. > > > --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Milestone or Component Hierarchy?
Hi Rupert, For the plugins that didn't have a 0.11 version we fixed them to work. For the majority of them we posted patches to the original plugins. If you browse the code http://code.optaros.com/trac/oforge/browser/trunk you will see that we splitted the plugins in two categories: - trac-hacks - here you will see some plugins imported from trac-hacks directly - forks - the plugins that didn't worked or had some bugs and we had to patch them On Fri, May 30, 2008 at 10:14 PM, rupert thurner <[EMAIL PROTECTED]> wrote: > > according to http://code.optaros.com/trac/oforge/wiki/AssembledComponents > you integrated a lot of plugins which do not support 0.11? did you > change them, or you run them like that? > > rupert. > > On May 30, 3:37 pm, "Culapov Andrei" <[EMAIL PROTECTED]> wrote: >> Hi, >> Maybe you need for every project a new trac environment. We developed >> a plugin that addresses that problem, that makes easy management of >> multiple trac >> environments.http://code.optaros.com/trac/oforge/browser/trunk/plugins/oforgeplugin >> >> On Thu, May 29, 2008 at 9:23 PM, <[EMAIL PROTECTED]> wrote: >> >> > Hello. At the company I work at we are starting to use Trac for >> > keeping track of all the tasks we need to do. But we have a lot of >> > products and projects. We have been using Trac for a few months and >> > already our milestone and component list is getting large. I am here >> > to ask if it is possible to set up a simple hierarchy of say two or >> > maybe three levels within the milestones or the components. I will >> > give two examples. >> >> > Multiple Components: >> > There is an overall milestone we want to accomplish that contains many >> > different types of tasks within a bunch of different products. >> > Currently one thought is two make the components the name of different >> > products/parts/prototypes thus within the overall milestone, the >> > components separate out the tickets per product or part. But this >> > setup means we are going to have a hundred or so components. There is >> > also no organization within the components with this setup. Ideally >> > the hierarchy in this sense would be Milestone >> >Part#1 Component >> >Tests, Research, Software Dev (three sub components). >> >> > Multiple Milestones: >> > I am in more favor of this approach. Instead of making tons of >> > components, do the hierarchy with Milestones. For an example we could >> > have the milestones setup like this. >> > ST-2400 (Top Milestone) >> >GPS Unit (sub milestone) >> >-Components separate tickets >> >-Tests, Research, Software Dev >> >GeoSync Unit >> >-Components... >> >Frame and Chassis >> >-Components... >> >Wireless Com Unit >> >-Components... >> >> > Is there anyway to accomplish this in Trac? Perhaps there is some sort >> > of mod or plugin that may accomplish this? >> >> > If we want to implement this hierarchy into the Trac code ourself, >> > would this be a huge task? > > > --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Milestone or Component Hierarchy?
Hi, Maybe you need for every project a new trac environment. We developed a plugin that addresses that problem, that makes easy management of multiple trac environments. http://code.optaros.com/trac/oforge/browser/trunk/plugins/oforgeplugin On Thu, May 29, 2008 at 9:23 PM, <[EMAIL PROTECTED]> wrote: > > Hello. At the company I work at we are starting to use Trac for > keeping track of all the tasks we need to do. But we have a lot of > products and projects. We have been using Trac for a few months and > already our milestone and component list is getting large. I am here > to ask if it is possible to set up a simple hierarchy of say two or > maybe three levels within the milestones or the components. I will > give two examples. > > Multiple Components: > There is an overall milestone we want to accomplish that contains many > different types of tasks within a bunch of different products. > Currently one thought is two make the components the name of different > products/parts/prototypes thus within the overall milestone, the > components separate out the tickets per product or part. But this > setup means we are going to have a hundred or so components. There is > also no organization within the components with this setup. Ideally > the hierarchy in this sense would be Milestone >Part#1 Component >Tests, Research, Software Dev (three sub components). > > Multiple Milestones: > I am in more favor of this approach. Instead of making tons of > components, do the hierarchy with Milestones. For an example we could > have the milestones setup like this. > ST-2400 (Top Milestone) >GPS Unit (sub milestone) >-Components separate tickets >-Tests, Research, Software Dev >GeoSync Unit >-Components... >Frame and Chassis >-Components... >Wireless Com Unit >-Components... > > Is there anyway to accomplish this in Trac? Perhaps there is some sort > of mod or plugin that may accomplish this? > > If we want to implement this hierarchy into the Trac code ourself, > would this be a huge task? > > > > --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: TracSvnPoliciesPlugin problem
Can you give more details please? like: * what configurations do you have in trac.ini? * what configurations dou you have in /etc/svnpolicies/svnpolicies.conf * do you have svnlook and svnnotify installed? * if you use the email notification on commit, do you have the trac smtp settings configured? * if you use the trac commands did you specified the path to the trac-post-commit-hook ? * the svn server runs under the same user as the trac was installed? the svn hook tries to open the trac environment and if it hasn't rights then you have problems here are the settings that we use trac.ini . [svnpolicies] #general settings author_url_template = https://oforge.com/user/%s change_url_template = https://oforge.com/trac/%s/changeset/%s domain = oforge.com email.diff_limit = 5000 svnlook = /usr/bin/svnlook svnnotify = /usr/bin/svnnotify # hook script that you can find in the trac_post_hook = /usr/local/bin/trac-post-commit-hook #enabled hooks allow_revprop_changes.enabled = true commands.enabled = true email.enabled = true email.list = [EMAIL PROTECTED] email.prefix = [oforge] email_from_address = [EMAIL PROTECTED] email_from_enabled = true email_subject_cx = true log_message.minimum = 10 log_message.pattern = .*word$ svn_property.enabled = true svnpolicies_enabled = true . and /etc/svnpolicies/svnpolicies.conf [paths] python_path = /usr/local/lib/python2.4/site-packages trac_base_dir = /var/www/oforge/trac On Wed, May 21, 2008 at 10:36 PM, Pablo Fabregat <[EMAIL PROTECTED]> wrote: > > Hi all, > > I managed to get this plugin installed and it throws no errors... but when i > do a commit, whatever policy i put, nothing happens, it just commits, and i > can tell that the hook's being executed (it's in /usr/bin/svn-hook) because i > edited that script to throw an error and, it does... > > i'm almost done with this! :O > > any ideas ? > thanks in advance! > > > -- > Pablo Fabregat > http://www.pablofabregat.com.ar > > --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Workflow Angst
try http://code.optaros.com/trac/oforge/browser/trunk/plugins/workflowcontrollerplugin try using the assign_by_transition operation. if the plugin looks interesting i can give you more info or point you to some documentation On Tue, May 20, 2008 at 10:41 PM, lfrancis <[EMAIL PROTECTED]> wrote: > > Thanks Eli -- I've been trying to work with the > AdvancedTicketWorkflowPlugin but have had no love, log says: > > ERROR: Skipping "advancedworkflow.controller = > advancedworkflow.controller": (can't import "cannot import name > check_call") > > Hmm. does this plugin require Python 2.5? We're running Python 2.4.4 > here. > > Thanks, > -Lewis > > > On May 17, 8:49 am, Eli <[EMAIL PROTECTED]> wrote: > > On Thursday 15 May 2008 05:43:41 pm lfrancis wrote: > > > > > > > > > I'm new to Trac and am trying to wrap my head around the tool, > > > especially custom workflows vis a vis our internal process and am > > > hoping for some guidance/pointers. > > > > > Our typical process (skinny) is a QA or a PM type writes tickets and > > > assigns to the appropriate person. In the case of QA, that appropriate > > > person might be the PM who then vets the bug and reassigns it as > > > needed, or a ticket might be directly assigned without a vetting step. > > > > > The assignee then accepts the ticket, fixes/addresses and reassigns > > > back to the reporter for validation, who then closes or fails. > > > > > I've been working with the Optional Testing actions on TracWorkflow to > > > set this up. Right now I've set testing.operations = set_owner and > > > reject.operations = set_owner, but I'd like to streamline reassignment > > > by automatically selecting the reporter in a reassignment select. > > > Likewise, it would be nice if the assignee was automatically selected > > > for the fail case. > > > > > Is there a blessed way of doing this in Trac .11rc, or is this a > > > square peg into a round hole ind of thing? Thanks much. > > > > The set_owner_to_report and set_owner_to_previous operations fromhttp:// > trac-hacks.org/wiki/AdvancedTicketWorkflowPluginmay help. > > > > Otherwise, you may need to write a plugin. > > > > HTH, > > > > Eli > > --. "If it ain't broke now, > > Eli Carter \ it will be soon." -- crypto-gram > > [EMAIL PROTECTED] `- > > > > --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Having Specific Workflows for Each Ticket Type
Hi guys, I created a workflow controller that knows to hide/to show actions based on ticket fields values, beside other new operations. You can find it at http://code.optaros.com/trac/oforge/browser/trunk/plugins/workflowcontrollerplugin All the new functionality can be configured from the trac.ini file. For more details feel free to contact me. On Wed, May 7, 2008 at 10:24 PM, Chris <[EMAIL PROTECTED]> wrote: > > Noah, > > So you're saying it's possible to create a plug-in that could assign a > particular workflow based on the ticket type? And that this would have > to be a plug-in as it's too complex for the ticket-workflow in > the .ini? I can visually see how this would work in the admin > interface, actually pretty slick, but as for implementing it > myself heh. Looks like my spare time is going to be devoted to > learning Python. :) > > Chris > > > On May 6, 6:21 pm, Noah Kantrowitz <[EMAIL PROTECTED]> wrote: > > On May 6, 2008, at 5:45 PM, Chris wrote: > > > > > > > > > Is it possible to define a particular workflow for Tasks and have a > > > different workflow for Defects? Would Trac take nicely to changing the > > > trac-workflow in mid-stream development? For example, the default > > > workflow is great for straight tasking, but when a defect gets entered > > > into the system we'd like to have it go through a Q/A process. So in > > > that instance the enterprise workflow sample would be desired. > > > > > I found this in the Trac wiki but am not sure if it exactly addresses > > > it (had a hard time following it). > > > > > "A workflow plugin can add an arbitrary workflow operation, so this is > > > already possible. > > > > There seems to be some confusion between the core workflow system > > (ITicketActionControler) and the include ConfigurableTicketWorkflow. > > The trac.ini-based system is designed to allow for simple > > configuration, but doesn't come close to allowing the full flexibility > > of the underlying framework. Personally I think this is fine, people > > are just very averse to learning Python just to be able to implement > > their workflows. This is also understandable, but I would rather see > > the community step up and provide workflow plugins for other common, > > but not simple enough to be in ConfigurableTicketWorkflow, use cases. > > > > --Noah > > > --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Ticket workflow: Return to check
This controller, from the trac sample plugins directory, creates a new operation. In trac operations are tied to actions, and actions define transitions of tickets from one status to another So you have to have an action declared in the configuration file, that has the code_review operation like: = -> .operations = code_review This operation can be tied to any action you what. You have to choose in which status you want to have this action available. On Sat, Feb 23, 2008 at 12:15 PM, DeyV <[EMAIL PROTECTED]> wrote: > > Thank's Andrei, I does the 3 steps, but still don't know, what now? > > I'm not see any new ticet Resolutions or statuses. Must I add the new > Resolutions in admin? > And from can I get the names for it? > > > > > On 23 Lut, 09:26, "Culapov Andrei" <[EMAIL PROTECTED]> wrote: > > 1. copy it in the plugins directory of your trac installation the > > controller > classhttp://trac.edgewall.org/browser/trunk/sample-plugins/workflow/CodeRe... > > > > > And then start editting the trac.ini file > > > > 2. enable this plugin class > > > > [components] > > > > codereview.CodeReviewActionController = enabled > > ... > > > > 3. add the this class the the workflow controllers list: > > > > [ticket] > > > > workflow = ConfigurableTicketWorkflow,CodeReviewActionController > > > > > > --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Ticket workflow: Return to check
Hi DeyV, to run this plugin, follow this steps: 1. copy it in the plugins directory of your trac installation the controller class http://trac.edgewall.org/browser/trunk/sample-plugins/workflow/CodeReview.py And then start editting the trac.ini file 2. enable this plugin class [components] codereview.CodeReviewActionController = enabled ... 3. add the this class the the workflow controllers list: [ticket] workflow = ConfigurableTicketWorkflow,CodeReviewActionController 4. add a code review action in the workflow section of the ini file I didn't understand exactlly in which status or statuses of the ticket you what to have this action so I can't write this configuration. Give more details please. You can take a look at the http://trac.edgewall.org/browser/trunk/sample-plugins/workflow/enterprise-review-workflow.ini in which this code review feature is used, to get some ideas. On Fri, Feb 22, 2008 at 3:29 PM, DeyV <[EMAIL PROTECTED]> wrote: > > I'd like add to Trac ticet option: Fixed-toReview > > After that: > - Ticet status: Open, ToReview > - Owner: Autor, or Previus Owner > > Maybe > http://trac.edgewall.org/browser/trunk/sample-plugins/workflow/CodeReview.py > can do something like that, but I don't know how run this plugin. > > What can I do? > > > > > --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Adding own actions, or states of ticket
Yes you can add new actions. You have to edit the configuration file, trac.ini, for adding new actions. You can take a look at an example of enterprise workflow http://trac.edgewall.org/browser/trunk/contrib/workflow/enterprise-workflow.ini A action is defined by two things: 1 a transition from a ticket status to another 2 the operation applied to this transition On Thu, Feb 21, 2008 at 11:45 AM, Kamil Dziedzic <[EMAIL PROTECTED]> wrote: > > Hello. > > Is there possible to add own actions? > For example beetwen "accept ticket" or "resolve as"? > > Or maybe there is a way to tag in which state is ticket? > For example "Done, but need testing", "Done in SVN, requires relase", "Done > in > 50%"... or any other? > > Could be done something like that in track? > > -- > Regards, Kamil Dziedzic > > > > --~--~-~--~~~---~--~~ 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Want to define a custom action in enterprise-workflow
I think that you can do that by creating a component that implements the ITicketChangeListener, and on the ticket_created and on the ticket_changed methods, you can test if the ticket has a owner and change the status of the ticket to the assigned status. I can help you with an example, if you have problems in implementing this functionality. On Thu, Feb 14, 2008 at 11:34 AM, Shaun Longhurst <[EMAIL PROTECTED]> wrote: > > We have taken the bold step of upgrading to trac0.11 and I think its > great. Our project manager is annoyed by one feature of the enterprise- > workflow. That is, when a new ticket is created and assigned, the > status of the ticket isnt actually assigned until you go back into the > ticket and assign it again. Is there an easy way to customise this > workflow so that when a new ticket is assigned. It does actually go to > the assigned stage rather than having to do this duplicated work. > > 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
