ticket summary type release owner status created modified _description _reporter 10312 [REQUEST] Ability to assign milestones to clients or clients to milestones defect 0.12 new 2012-09-12T19:47:23+02:00 2017-01-12T22:00:46+01:00 "The basic idea is this: * We have a system with multiple clients and projects set up. * We use milestones to determine functionality that client has ordered. * We have many milestones at this time so we want to filter them out by assigning clients to them or the other way. * Using new assignment we will then be able to filter out ticket creation combo box from unnecessary milestones." dr4cul4@… 7278 """Ticket Change"" summary doesn't work if no milestone is assigned or milestone has no due date" defect 0.11 new 2010-06-22T12:28:11+02:00 2017-01-12T22:00:46+01:00 "The Summary ""Ticket Changes"" does not deal with tickets - having no milestone assinged - having a milestone with no due date. This is cause a restriction in the SELECT startement in ´summary_ticketchanges.py´. I´ve attached three excamples of the resulting xml-file. Only the version with due date shows the right result. If I change the SQL-Statement (see attached diff), I could get the 2nd problem solved (tickets with milestones with no due date are now processed) If there is no milestone assigned, any changes to the ticket won´t be added to the XML output - no idea why. " hju 7277 "[PATCH] Action ""Send Email"" of event syste not running if SMPT-Server requires authentication" defect 0.11 new 2010-06-22T12:03:51+02:00 2017-01-12T22:00:46+01:00 "We are using an SMTP-Server which requires authentication. {{{ Traceback (most recent call last): File ""/root/inst/clientsplugin/0.11/cron/run-client-event"", line 97, in RunClientEvents() File ""/root/inst/clientsplugin/0.11/cron/run-client-event"", line 91, in __init__ ClientEvent.triggerall(self.env, self.req, options.event) File ""build/bdist.linux-i686/egg/clients/events.py"", line 284, in triggerall File ""build/bdist.linux-i686/egg/clients/events.py"", line 246, in trigger File ""build/bdist.linux-i686/egg/clients/action_email.py"", line 168, in perform File ""/usr/lib/python2.5/smtplib.py"", line 310, in connect raise socket.error, msg socket.error: (111, 'Verbindungsaufbau abgelehnt') }}} The attached patch of ´action_email.py´ solves the problem in our environment." hju 7274 events system not running if no repository installed defect 0.11 new 2010-06-21T22:43:20+02:00 2017-01-12T22:00:46+01:00 "This is a nice pluging with a lot of very good ideas! I apologize for creating another ticket. We are using trac without any version control system (svn) because we are not managing software projects. The event system is not running, if there is no repository defined. {{{ python /root/inst/clientsplugin/0.11/cron/run-client-event -c ""Ticket Changes"" -e /path/to/env Traceback (most recent call last): File ""/root/inst/clientsplugin/0.11/cron/run-client-event"", line 97, in RunClientEvents() File ""/root/inst/clientsplugin/0.11/cron/run-client-event"", line 87, in __init__ repos = self.env.get_repository() File ""/usr/lib/python2.5/site-packages/trac/env.py"", line 305, in get_repository return RepositoryManager(self).get_repository(authname) File ""/usr/lib/python2.5/site-packages/trac/versioncontrol/api.py"", line 149, in get_repository name=self.repository_type)) trac.core.TracError: Unsupported version control system ""svn"": Can't find an appropriate component, maybe the corresponding plugin was not enabled? }}} Obviously there is a check missing if a repository is defined. If I remove two lines of code in ´run-client-event´ line 87 and 88 I can pass this error. {{{ class RunClientEvents: def __init__(self): locale.setlocale(locale.LC_ALL, '') self.env = open_environment(options.envpath) self.req = SendClientFakeReq() # Sync the repo so that any commits that happen to have been made # that include client comments are included. #>> repos = self.env.get_repository() #>> repos.sync() }}} " hju 7271 [Patch] Reports not working with Postgres 8.4 (TimingAndEstimation plugin) defect 0.11 new 2010-06-20T19:36:29+02:00 2017-01-12T22:00:46+01:00 "The reports '''Ticket Hours Grouped By Client''' and '''Ticket Hours Grouped By Client with Description''' that are viewed by [wiki:TimingAndEstimationPlugin TimingAndEstimation plugin] are sending invalid SQL statement to the database. The description of the problem is attached in this ticket. The following piece of code resolved the problem: {{{ #!diff Index: reports.py =================================================================== --- reports.py (revision 8134) +++ reports.py (working copy) @@ -70,7 +70,7 @@ component as __component__,version, severity, milestone, status, owner, CAST(estimatedhours.value as DECIMAL) as estimate_work, CAST(totalhours.value as DECIMAL) as Total_work, - CASE WHEN billable.value = 1 THEN 'Y' + CASE WHEN billable.value = ($BILLABLE) THEN 'Y' else 'N' END as billable, time AS created, changetime AS modified, -- ## Dates are formatted @@ -131,7 +131,7 @@ WHERE t.status IN ($NEW, $ASSIGNED, $REOPENED, $CLOSED) AND billable.value in ($BILLABLE, $UNBILLABLE) - GROUP BY client.value + GROUP BY client.value, t.component ) as tbl ORDER BY __group__, _ord ASC,ticket """""" @@ -153,7 +153,7 @@ component as __component__,version, severity, milestone, status, owner, CAST(estimatedhours.value as DECIMAL) as estimate_work, CAST(totalhours.value as DECIMAL) as Total_work, - CASE WHEN billable.value = 1 THEN 'Y' + CASE WHEN billable.value = ($BILLABLE) THEN 'Y' else 'N' END as billable, time AS created, changetime AS modified, -- ## Dates are formatted @@ -214,7 +214,7 @@ WHERE t.status IN ($NEW, $ASSIGNED, $REOPENED, $CLOSED) AND billable.value in ($BILLABLE, $UNBILLABLE) - GROUP BY client.value + GROUP BY client.value, t.component ) as tbl ORDER BY __group__, _ord ASC,ticket """""" }}}" ricardo.ichizo@… 6774 Improvements : external tracker and zero client rate enhancement 0.11 new 2010-03-05T16:12:21+01:00 2017-01-12T22:00:46+01:00 "I have written two improvements (well, at least I think they're improvements ;-) ) to ClientsPlugin : * make it possible to set the client rate to zero * add an ""external tracker"" field for each client (optional) when the client has its own bugtracker. The two features are independant, except on 1 file where they overlap, otherwise I'd have provided two patches. To understand the motives behind the patch, I must explain how I use Trac. I'm responsible for a shared project in a rather big organization, so I have internal clients : other projects using my shared project. As a result, my clients are not ""billable"", and they always have their own tracker where they open bugs for my project. When they do, I open a bug in mine, assign it to someone in my team, and forward the resolution to their tracker. Thus, I must track the bug reference in my client's tracker. === No client rate === The first part of the patch makes it possible to set the default client rate to zero. In this case, a small piece of javascript hides the field in the ticket form. It does not affect the previous feature : if you don't set a default client rate, the field is not hidden and you can set it manually. No default rate and a default rate of zero are two different things. I have thought of another way to do it : on the client form, add a checkbox to set it to ""not billable"". I did not do that because it was more invasive in your code, but I think it may have a better usability. === External tracker === The second part of the patch adds an optional field to the client form (and the database) where an URL to the client tracker can be set. This URL may contain the ""%s"" string, which will be replaced by the bug number on the ticket form. The ticket form has an extra custom field where the client bug number can be set. On ticket display, an href link is created using the template client tracker URL. Please tell me what you think of this patch, if you agree to include it, if it needs more work, etc. Thanks" Aurélien Bompard 4805 [Patch] ClientsPlugin not working with Postgres 8.3 (possibly other versions) as trac backend defect 0.11 new 2009-03-19T00:32:55+01:00 2017-01-12T22:00:46+01:00 "The clientsplugin is emitting some SQL that is bad when it comes to postgresql 8.3 (haven't tried with lower versions, it may be the same). I have modified the api.py and model.py files to try and make this work. The 'broken' behavior is as follows: * Cannot upgrade During inital schema creation, a rollback is being issue when trying to populate the 'client_events' table. This is because surrounding a string with a "" (double quote) in postgres is just asking for a column. The solution was to change the "" to ' (double quotes to single quotes). [source:/clientsplugin/0.11/clients/api.py@4486#L89 API.PY Line 89-101] * Next, the problem is that during client 'creation' (via webadmin) there was an error being thrown: {{{ """" Invalid input syntax for INTEGER }}} After tracing, I found that the 'self.default_rate' and 'self.currency' variables where being defaulting to ' ' (empty string) if not found. I changed this to default to 0. [[BR]] [source:/clientsplugin/0.11/clients/model.py@4486#L37 MODEL.PY Line 37-38] * The last problem was on updating the client, if you erased the '0' in the billrate box, and submitted, you would get the same error as before. I just added to checks (one for default_rate and one for currency) right before the execution of the UPDATE statement.[[BR]] [source:/clientsplugin/0.11/clients/model.py@4486#L95 MODEL.PY Line 95] This is working on my setup now, but there are a couple of things to note: * It was a new setup with no existing tickets * PostgreSQL 8.3.6 * Trac being run through apache with ldap based authentication If you have questions or want more info, please feel free to contact me. " scott.mead@… 3974 Add Id to client and add possibility to create links to clients like : client:1 enhancement 0.11 new 2008-10-23T14:32:18+02:00 2017-01-12T22:00:46+01:00 "Hello, Think that is a good idea to add Id field to client and make possible to create links using wikiprocessor like: client:1 Thanks." BKV