[Trac] Re: Looking for the record creator
On Oct 7, 9:33 am, Stephen Moretti [EMAIL PROTECTED] wrote: 2008/10/7 didley [EMAIL PROTECTED] Sometimes it's necessary that a user with ticket-admin permission has to create tickets with to fill out reporter and assign a owner. When this is done I can't see the creator (ticket-admin) of the ticket. After a while all user thinking the inscribed reporter is the creator but it isn't. Is there a field in the table schema of trac where I can find the creator? Nope. The reporter is the creator under most circumstances. Have you thought of leaving the reporter as the ticket-admin and adding the person who emailed/called the ticket as a cc member? Or possibly adding a custom field for the creatpr? Stephen That's pity. I have to think obout if add a custom field for it. I suppose it's the only way I have. Thanx didley --~--~-~--~~~---~--~~ 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: Looking for the record creator
On Oct 7, 2008, at 11:51 PM, didley wrote: On Oct 7, 9:33 am, Stephen Moretti [EMAIL PROTECTED] wrote: 2008/10/7 didley [EMAIL PROTECTED] Sometimes it's necessary that a user with ticket-admin permission has to create tickets with to fill out reporter and assign a owner. When this is done I can't see the creator (ticket-admin) of the ticket. After a while all user thinking the inscribed reporter is the creator but it isn't. Is there a field in the table schema of trac where I can find the creator? Nope. The reporter is the creator under most circumstances. Have you thought of leaving the reporter as the ticket-admin and adding the person who emailed/called the ticket as a cc member? Or possibly adding a custom field for the creatpr? Stephen That's pity. I have to think obout if add a custom field for it. I suppose it's the only way I have. It would be pretty easy to automate in a plugin, just make an ITicketManipulator that sets the field value on create to req.authname. --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] Need help on Change History Trac
Trac Users, I'm Damodharan Kuttiyappan, working as a Configuration Manager in ATX Group Inc, Texas. We are evaluating Trac Integrated SCM and Project Management for our Bug tracking purpose. It’s an excellent open source tool for bug tracking. I would like to implement few features on Trac. Our first target is to add a button next to Change History (Show/Hide button). When we click on the button, it should show the change history log. By default we want to make the changes log as an hidden think as the Trac users feel Change history occupies most of the pages when the bugs have been transferred between users. I need your advise to implement this change. Help me to locate the file where do I need to make the changes. I'm looking forward to your reply. Thanks, Damodharan. --~--~-~--~~~---~--~~ 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] how is trac SUPPOSED to be used?
This is going to sound like a rather vague question, but how is trac SUPPOSED to be used? The reason I ask is because we use trac at my company, but we are thinking of switching to something else. Nobody at my company seems to like it. I just came on board a month ago, and I've never used trac, and it's kind of been placed upon me to research alternatives, but I figure that trac is used everywhere so it's got to be good and we are probably just using it wrong. However, a month has gone by, and I really can't figure trac out. It doesn't seem to work, or do anything at all, for that matter. I'm kind of stymied. I've heard this from other people as well; trac is just baffling and weird. I think I've read that track is supposed to adapt to YOUR workflow, and work the way YOU want it to, but it seems to me that it has no workflow at all. For example, my boss recently asked me what changes were going to be moved into the trunk since the last merge two weeks ago, and I thought to myself, Oh, I'll just do a search for all the bugs that I fixed in the past two weeks, but, amazingly, I CAN'T DO THAT. Even using custom query there is no field that allows you to query based on time. And I certainly don't want to start writing SQL. I read over the documentation, and it does a good job of explaining WHAT things do, but I can't find anywhere that explains what it was DESIGNED to do. How were tickets DESIGNED to be used, if they weren't designed to be used based on date? To me, the date seems the most obvious thing to track bugs by, other than perhaps by severity. The date reported, the date fixed, the date released. I'm wondering if it's a philosophical conflict. The people at my company (myself included) like opinionated software. It's like iTunes. Everybody hates iTunes because they can't manage their music in their own unbelievably specific manner. However, if you use iTunes as it was DESIGNED to be used, you will discover that it's an amazing, excellent piece of software. I can't imagine managing my music any other way. It just works so well. You just have to get by the fact that you have to do things the Apple way. Believe it or not, the Apple way is usually pretty good. I'm concerned that the trac way is... well, I don't think it even has a way. Does it? I can go to the subversion documentation, or the git documentation, and it will tell me EXACTLY how I'm supposed to manage my source code, how my teams are supposed to work together, how merging is supposed to work, what the workflow is, et cetera. There are a couple of options of course, but at least they are well documented options. Anyway, sorry for the strange question. Can anybody explain to me how a usual trac workflow is supposed to look? Or a good website that goes over how people generally use trac? Thanks! Philip www.readMedia.com -- Local Press Releases. --~--~-~--~~~---~--~~ 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: how is trac SUPPOSED to be used?
On Oct 7, 2008, at 12:37 PM, Stedwick wrote: This is going to sound like a rather vague question, but how is trac SUPPOSED to be used? The reason I ask is because we use trac at my company, but we are thinking of switching to something else. Nobody at my company seems to like it. I just came on board a month ago, and I've never used trac, and it's kind of been placed upon me to research alternatives, but I figure that trac is used everywhere so it's got to be good and we are probably just using it wrong. However, a month has gone by, and I really can't figure trac out. It doesn't seem to work, or do anything at all, for that matter. I'm kind of stymied. I've heard this from other people as well; trac is just baffling and weird. I think I've read that track is supposed to adapt to YOUR workflow, and work the way YOU want it to, but it seems to me that it has no workflow at all. This is correct, one of the central design tenets of Trac is that it enforces as little process on you as possible. This does seem to backfire sometimes, as there is a large segment of the userbase that would like more structure than that. If you have a suggestion on how to resolve this, please let us know, it is frequently debated but people rarely seem to come up with anything solid. For example, my boss recently asked me what changes were going to be moved into the trunk since the last merge two weeks ago, and I thought to myself, Oh, I'll just do a search for all the bugs that I fixed in the past two weeks, but, amazingly, I CAN'T DO THAT. Even using custom query there is no field that allows you to query based on time. And I certainly don't want to start writing SQL. Time-based queries were indeed one of the major deficienes of the query system vs. reports. I believe this feature has been checked in to trunk, and so will be part of 0.12 when it is released. In the mean time, yes you have to write SQL. The query system is no where near a full replacement for reports, which is why despite their ugliness reports have not been removed yet. I read over the documentation, and it does a good job of explaining WHAT things do, but I can't find anywhere that explains what it was DESIGNED to do. How were tickets DESIGNED to be used, if they weren't designed to be used based on date? To me, the date seems the most obvious thing to track bugs by, other than perhaps by severity. The date reported, the date fixed, the date released. I'm wondering if it's a philosophical conflict. The people at my company (myself included) like opinionated software. It's like iTunes. Everybody hates iTunes because they can't manage their music in their own unbelievably specific manner. However, if you use iTunes as it was DESIGNED to be used, you will discover that it's an amazing, excellent piece of software. I can't imagine managing my music any other way. It just works so well. You just have to get by the fact that you have to do things the Apple way. Believe it or not, the Apple way is usually pretty good. I'm concerned that the trac way is... well, I don't think it even has a way. Does it? I can go to the subversion documentation, or the git documentation, and it will tell me EXACTLY how I'm supposed to manage my source code, how my teams are supposed to work together, how merging is supposed to work, what the workflow is, et cetera. There are a couple of options of course, but at least they are well documented options. Anyway, sorry for the strange question. Can anybody explain to me how a usual trac workflow is supposed to look? Or a good website that goes over how people generally use trac? You can look at the TracUsers page to see other people using Trac. Some major places I know you can look include Trac itself, dev.laptop.org, developer.pidgin.im, trac.adiumx.com. Beyond that you will need to sit down and figure out what works best for you and your team. --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: Need help on Change History Trac
You could probably put some JS hackery in the ticket.html template. Doing this right would entail making a plugin to add the JS to the ticket page and possibly setting up a stream filter for fallback. --Noah On Oct 7, 2008, at 12:43 PM, Damu wrote: Trac Users, I'm Damodharan Kuttiyappan, working as a Configuration Manager in ATX Group Inc, Texas. We are evaluating Trac Integrated SCM and Project Management for our Bug tracking purpose. It’s an excellent open source tool for bug tracking. I would like to implement few features on Trac. Our first target is to add a button next to Change History (Show/Hide button). When we click on the button, it should show the change history log. By default we want to make the changes log as an hidden think as the Trac users feel Change history occupies most of the pages when the bugs have been transferred between users. I need your advise to implement this change. Help me to locate the file where do I need to make the changes. I'm looking forward to your reply. Thanks, Damodharan. --~--~-~--~~~---~--~~ 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: how is trac SUPPOSED to be used?
Noah Kantrowitz wrote: On Oct 7, 2008, at 12:37 PM, Stedwick wrote: This is going to sound like a rather vague question, but how is trac SUPPOSED to be used? [snip] For a more structured, restricted, but still powerful way of using Trac to manage bugs as well as handle project management, have a look at http://www.agile42.com/ which implements Agile Development using a customised version of Trac (based on 0.9.x) If you don't know much about Agile development, this will probably confuse you more than help, so it's worth reading some of their links (Scrum in a nutshell, etc) or http://en.wikipedia.org/wiki/Agile_software_development or whatever else google throws at you. HTH, -- Iain Buchanan iain at pcorp dot com dot au Phasers locked on target, Captain. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~--- begin:vcard fn:Iain Buchanan n:Buchanan;Iain email;internet:[EMAIL PROTECTED] tel;work:+61 (0)8 8947 0933 x-mozilla-html:FALSE version:2.1 end:vcard
[Trac] Re: how is trac SUPPOSED to be used?
Noah Kantrowitz kirjoitti: On Oct 7, 2008, at 12:37 PM, Stedwick wrote: This is going to sound like a rather vague question, but how is trac SUPPOSED to be used? The reason I ask is because we use trac at my company, but we are thinking of switching to something else. Nobody at my company seems to like it. I just came on board a month ago, and I've never used trac, and it's kind of been placed upon me to research alternatives, but I figure that trac is used everywhere so it's got to be good and we are probably just using it wrong. However, a month has gone by, and I really can't figure trac out. It doesn't seem to work, or do anything at all, for that matter. I'm kind of stymied. I've heard this from other people as well; trac is just baffling and weird. I think I've read that track is supposed to adapt to YOUR workflow, and work the way YOU want it to, but it seems to me that it has no workflow at all. This is correct, one of the central design tenets of Trac is that it enforces as little process on you as possible. This does seem to backfire sometimes, as there is a large segment of the userbase that would like more structure than that. If you have a suggestion on how to resolve this, please let us know, it is frequently debated but people rarely seem to come up with anything solid. This is something that is Trac power and weakness. Most Trac like software establish some sort of workflow that you must follow, Trac instead is a liberate in that matter. One problem with corporate users often seek ready to use solutions that have quite straight forward workflows and ways to use software. With Subversion you can do pretty much everything that you do with normal files, svnbook just represent one trunk, tags and branches way to work, but people seem to use that quite often. http://trac.edgewall.org/wiki/TracBooks contains one book to read about realworld usage. I haven't read it though so hard to tell is it any good. -- Jani Tiainen Tein sein mihin näillä lahjoilla pystyin. Tein sen, en yhtään enempää. - Martti Servo Napander --~--~-~--~~~---~--~~ 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: custom group for ticket permission
Stephen Moretti kirjoitti: 2008/10/8 Jani Tiainen [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Rainer Sokoll kirjoitti: On Wed, Oct 08, 2008 at 01:59:48AM -0700, Jean Marie wrote: I want to disallow a group of user to select a certain action for a ticket, e.g. a developer is not allowed to close a ticket. I have a similar issue. A developer must not close a ticket, instead, once he marked a ticket resolved, the ticket must go over to the QA people. They will perform their tests and finally, either close the ticket or re-assign it to the developer. This is still not resolved for me (has not prio number 1), but I think it is doable by changing the default workflow. Correct. First you need to create new permission, e.g. TICKET_CLOSE. And to create your own permissions : http://nil.checksite.co.uk/post.cfm/trac-0-11-creating-your-own-permissions Doesn't that BlackMagicTicketPlugin make possible to create arbitary permissions for tickets? -- Jani Tiainen Tein sein mihin näillä lahjoilla pystyin. Tein sen, en yhtään enempää. - Martti Servo Napander --~--~-~--~~~---~--~~ 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: How can I configure Trac to use subversion 1.5
Out of curiosity, what do you expect to get from running 1.5 on the server side? There are a lot of changes in subversion that are client side only. The biggest server side change is that the neon library was replaced by the serf library, but neon is still available. This won't make much of a difference for most ppl, and I would argue that neon will be more stable, for a little while anyway. I think you're wrong: serf and neon are client-side changes, not server-side. Bot are HTTP/webdav client libraries, the server does not use them. Moreover, the new merge system needs a SVN 1.5 server, which is definitely a big change. There are others changes that I use, for example the write-through proxy is a very handy feature 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: custom group for ticket permission
Hi Jani, First you need to create new permission, e.g. TICKET_CLOSE. How can i do this? Best regards Jean Marie --~--~-~--~~~---~--~~ 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: how is trac SUPPOSED to be used?
I think I might be restating a bit here from what others have already said, but Trac does (or can do) what you want it to do. It is flexible and doesn't force its own business logic on its users. It basically has to be like that, or it will be targeting only a small portion of the population regardless of whichever specific implementation it would choose to implement. A problem with that approach is that not only do you have to learn a new tool, but you also have to understand the processes your company has in place and then determine ways to configure/utilize Trac to fit in with those processes. In some cases you might have to recognize that you don't have processes so you'll have to invent them, then figure out what you want Trac to do, then figure out how to make Trac do that...quite daunting in some cases. The good news is that Trac will allow you to do those things. Unfortunately that means there's some work involved. It is not something that you can unzip and put in a directory and have it run tailored to your specific business logic right out of the box. So, maybe the question shouldn't be How is Trac supposed to be used?. Maybe it should be What are the processes for my company, and how can I tailor Trac to enforce those processes and make them easier to do? Chad -Original Message- From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Stedwick Sent: Tuesday, October 07, 2008 3:38 PM To: Trac Users Subject: [Trac] how is trac SUPPOSED to be used? This is going to sound like a rather vague question, but how is trac SUPPOSED to be used? --~--~-~--~~~---~--~~ 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: how is trac SUPPOSED to be used?
I broke this out into a separate email because otherwise it would be one huge email that rambled, which I have a tendency to do anyway... I might try to do this specific example with milestones. Define a Trac milestone as a merge point in the software, like the one you had two weeks ago. Assign the tickets to the next milestone in line, and when a merge point happens, create another milestone and send all unresolved tickets to that new milestone. At any given time you can quickly see what tickets have been closed by milestone. I wouldn't exactly say that's how I would use the milestone feature in a perfect world (I like to at least of the pretense of planning), but it would likely work used that way. Another approach could be to use the version field. Make set the version field up to have whatever you want to call the merge points, like the one you had two weeks ago. Code name them. Refer to a build number. Use a targeted merge date...whatever. As you close tickets, set the version to the merge point next in line when it was closed. This isn't exactly right either, as Version would typically (I think) be used to designate what software version the issue was found in, not the version the issue would be fixed in. However, that being said, you are free to use it how you like and define. A third could be a custom field. Make a custom field for whatever you want to call the merge points as said above. As you close tickets, set the field to the name of the merge point next in line when it was closed. This approach is a little harder because querying based on custom fields is tough, or so I have read...I've not done it. I'm fairly confident, as you pointed out, that if I decided I needed to search custom fields for something I could find adequate documentation to help me do so, I've just not had the need. Hope I was at least a little helpful. Chad -Original Message- From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Stedwick Sent: Tuesday, October 07, 2008 3:38 PM To: Trac Users Subject: [Trac] how is trac SUPPOSED to be used? For example, my boss recently asked me what changes were going to be moved into the trunk since the last merge two weeks ago, and I thought to myself, Oh, I'll just do a search for all the bugs that I fixed in the past two weeks, but, amazingly, I CAN'T DO THAT. Even using custom query there is no field that allows you to query based on time. And I certainly don't want to start writing SQL. --~--~-~--~~~---~--~~ 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: How can I configure Trac to use subversion 1.5
[EMAIL PROTECTED] wrote: On Oct 7, 5:16 pm, Emmanuel Blot [EMAIL PROTECTED] wrote: I have 2 subversion executable in my system. one is subversion 1.4.6 : /usr/bin/svn one is subversion 1.5.2: /home/meryl/bin/svn1.5/bin Trac does not use the SVN executables - at all. It relies on Python SVN modules and libraries, so you need to install the Python packages for svn1.5. The procedure depends on your Unix/Linux distribution (rpm, aptitude, emerge, ...) HTH, Manu Thank you for both response. I am running on ubuntu. How can I get the python subversion 1.5 binding? The package manager (atitute) only has 1.4.x binding. Thank you. Out of curiosity, what do you expect to get from running 1.5 on the server side? There are a lot of changes in subversion that are client side only. The biggest server side change is that the neon library was replaced by the serf library, but neon is still available. This won't make much of a difference for most ppl, and I would argue that neon will be more stable, for a little while anyway. --~--~-~--~~~---~--~~ 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: custom group for ticket permission
Doesn't that BlackMagicTicketPlugin make possible to create arbitary permissions for tickets? With 'BlackMagicTicketPlugin' currently you can only control single fields of a ticket. Best regards Jean Marie --~--~-~--~~~---~--~~ 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: How can I configure Trac to use subversion 1.5
On Tue, Oct 07, 2008 at 05:18:49PM -0700, [EMAIL PROTECTED] wrote: I am running on ubuntu. How can I get the python subversion 1.5 binding? The package manager (atitute) only has 1.4.x binding. Use the sources. It is fairly easy to build one's own subversion and SWIG bindings. 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: custom group for ticket permission
Rainer Sokoll kirjoitti: On Wed, Oct 08, 2008 at 01:59:48AM -0700, Jean Marie wrote: I want to disallow a group of user to select a certain action for a ticket, e.g. a developer is not allowed to close a ticket. I have a similar issue. A developer must not close a ticket, instead, once he marked a ticket resolved, the ticket must go over to the QA people. They will perform their tests and finally, either close the ticket or re-assign it to the developer. This is still not resolved for me (has not prio number 1), but I think it is doable by changing the default workflow. Correct. First you need to create new permission, e.g. TICKET_CLOSE. Then you need to create group in trac what has that permission (or assign permission to certain users). Finally use permission property in new trac workflow to enable close action only for TICKET_CLOSE permission. like putting (replacing existing) following piece to workflow-section: resolve = new,assigned,reopened - closed resolve.operations = set_resolution resolve.permissions = TICKET_CLOSE if you want to create group you do it this way in trac-admin (or by using webadmin): permission add my_group TICKET_CLOSE permission add dev1 my_group permission add dev2 my_group very simple. -- Jani Tiainen Tein sein mihin näillä lahjoilla pystyin. Tein sen, en yhtään enempää. - Martti Servo Napander --~--~-~--~~~---~--~~ 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: how is trac SUPPOSED to be used?
Sorry if this double posts! The first attempt at responding seems to not have worked... I think I might be restating a bit here from what others have already said, but Trac does (or can do) what you want it to do. It is flexible and doesn't force its own business logic on its users. It basically has to be like that, or it will be targeting only a small portion of the population regardless of whichever specific implementation it would choose to implement. A problem with that approach is that not only do you have to learn a new tool, but you also have to understand the processes your company has in place and then determine ways to configure/utilize Trac to fit in with those processes. In some cases you might have to recognize that you don't have processes so you'll have to invent them, then figure out what you want Trac to do, then figure out how to make Trac do that...quite daunting in some cases. The good news is that Trac will allow you to do those things. Unfortunately that means there's some work involved. It is not something that you can unzip and put in a directory and have it run tailored to your specific business logic right out of the box. So, maybe the question shouldn't be How is Trac supposed to be used?. Maybe it should be What are the processes for my company, and how can I tailor Trac to enforce those processes and make them easier to do? Chad -Original Message- From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Stedwick Sent: Tuesday, October 07, 2008 3:38 PM To: Trac Users Subject: [Trac] how is trac SUPPOSED to be used? This is going to sound like a rather vague question, but how is trac SUPPOSED to be used? --~--~-~--~~~---~--~~ 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: custom group for ticket permission
First you need to create new permission, e.g. TICKET_CLOSE. How can i do this? I found an intermediate solution by hacking the database: INSERT INTO permission (username, action) VALUES (group_qa, TICKET_CLOSE); After this, the manuall added permissions assignment is visible in the admin section and also the trac-admin shows me this assignment. In trac.ini i've set: [ticket-workflow] close.permissions = TICKET_CLOSE Now only users that are members of group group_qa are able to close a ticket. For the moment this solution is fine by me. Are there any doubts about this solution? Maybe there'll be a more elegant way of adding user defined permissions. Best regards Jean Marie --~--~-~--~~~---~--~~ 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: How can I configure Trac to use subversion 1.5
I am running on ubuntu. How can I get the python subversion 1.5 binding? The package manager (atitute) only has 1.4.x binding. You probably need to upgrade your system to a newer release, or force the use more recent (but declared less stable) packages. I don't know Ubuntu, but it is based on Debian, so it is likely you have to edit /etc/apt/sources.list, add the new version of packages, use aptitude update, then select the proper version of packages (aptitude install python-subversion/intrepid or the like). Note that due to dependency management, you may have to upgrade several other packages, so don't do this on a production server: try it first on a test machine... Or wait for a couple of weeks, I think a new major release of Ubuntu is about to be delivered. 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: how is trac SUPPOSED to be used?
Could there possibly be a way to develop and distribute specific configurations of the trac.ini file and a trac.db file? Maybe it's as simple as that. I would think some sort of white paper would be needed (maybe documented in the wiki) that explains how the specific process the specific configuration is supposed to work. Maybe a large(ish) percentage of processes could be covered by a small(ish) number of specific implementations. I think it is akin to how Apache and mysql was for me when I was trying to install a certain web-based bug tracking system for the first time. I didn't know how to run a web server and deal with a db server. More importantly, I didn't want to learn...had neither the time nor the desire. So finding the prebuilt and configured Apache release XAMPP by Apache Friends was the only thing that allowed me to move forward. Is it as simple as defining and documenting a process, configuring it, zipping the necessary pieces, and putting it up for distribution? Ok, not so simple to define said process, but configuring Trac once the hard part is done is relatively easy I think. It would be nice to have certain plugins preinstalled too, though I'm sure there's issues with redistributing others' plugins, even with the positive goal of more adoption of Trac. I've not tinkered with dropping portions of a configured Trac system into an existing Track install to see how it reacts... This would allow the ability for Trac development to continue on the generic path it is currently on, yet allow someone to pick a pre-setup configuration that more closely fits the way they do business so they don't have to get their hands dirty in the nitty-gritty details. Chad -Original Message- From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Noah Kantrowitz Sent: Wednesday, October 08, 2008 3:20 AM To: trac-users@googlegroups.com Subject: [Trac] Re: how is trac SUPPOSED to be used? This is correct, one of the central design tenets of Trac is that it enforces as little process on you as possible. This does seem to backfire sometimes, as there is a large segment of the userbase that would like more structure than that. If you have a suggestion on how to resolve this, please let us know, it is frequently debated but people rarely seem to come up with anything solid. --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: how is trac SUPPOSED to be used?
Also sorry if this double posts! The first attempt also seems to not have worked... I broke this out into a separate email because otherwise it would be one huge email that rambled, which I have a tendency to do anyway... I might try to do this specific example with milestones. Define a Trac milestone as a merge point in the software, like the one you had two weeks ago. Assign the tickets to the next milestone in line, and when a merge point happens, create another milestone and send all unresolved tickets to that new milestone. At any given time you can quickly see what tickets have been closed by milestone. I wouldn't exactly say that's how I would use the milestone feature in a perfect world (I like to at least have the pretense of planning), but it would likely be sufficient if used that way. Another approach could be to use the version field. Make set the version field up to have whatever you want to call the merge points, like the one you had two weeks ago. Code name them. Refer to a build number. Use a targeted merge date...whatever. As you close tickets, set the version to the merge point next in line when it was closed. This isn't exactly right either, as Version would typically (I think) be used to designate what software version the issue was found in, not the version the issue would be fixed in. However, that being said, you are free to use it how you like and define. A third could be a custom field. Make a custom field for whatever you want to call the merge points as said above. As you close tickets, set the field to the name of the merge point next in line when it was closed. This approach is a little harder because querying based on custom fields is tough, or so I have read...I've not done it. I'm fairly confident, as you pointed out, that if I decided I needed to search custom fields for something I could find adequate documentation to help me do so, I've just not had the need. Hope I was at least a little helpful. Chad -Original Message- From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Stedwick Sent: Tuesday, October 07, 2008 3:38 PM To: Trac Users Subject: [Trac] how is trac SUPPOSED to be used? For example, my boss recently asked me what changes were going to be moved into the trunk since the last merge two weeks ago, and I thought to myself, Oh, I'll just do a search for all the bugs that I fixed in the past two weeks, but, amazingly, I CAN'T DO THAT. Even using custom query there is no field that allows you to query based on time. And I certainly don't want to start writing SQL. --~--~-~--~~~---~--~~ 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: custom group for ticket permission
2008/10/8 Jani Tiainen [EMAIL PROTECTED] Stephen Moretti kirjoitti: 2008/10/8 Jani Tiainen [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Rainer Sokoll kirjoitti: On Wed, Oct 08, 2008 at 01:59:48AM -0700, Jean Marie wrote: I want to disallow a group of user to select a certain action for a ticket, e.g. a developer is not allowed to close a ticket. I have a similar issue. A developer must not close a ticket, instead, once he marked a ticket resolved, the ticket must go over to the QA people. They will perform their tests and finally, either close the ticket or re-assign it to the developer. This is still not resolved for me (has not prio number 1), but I think it is doable by changing the default workflow. Correct. First you need to create new permission, e.g. TICKET_CLOSE. And to create your own permissions : http://nil.checksite.co.uk/post.cfm/trac-0-11-creating-your-own-permissions Doesn't that BlackMagicTicketPlugin make possible to create arbitary permissions for tickets? TBH - I haven't looked at BlackMagicTicketPlugin yet, but, and this is the first time I've looked, the wiki does seem to suggest this. Using BMTP just for this would make me nervous --~--~-~--~~~---~--~~ 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: custom group for ticket permission
On Wed, Oct 08, 2008 at 01:59:48AM -0700, Jean Marie wrote: I want to disallow a group of user to select a certain action for a ticket, e.g. a developer is not allowed to close a ticket. I have a similar issue. A developer must not close a ticket, instead, once he marked a ticket resolved, the ticket must go over to the QA people. They will perform their tests and finally, either close the ticket or re-assign it to the developer. This is still not resolved for me (has not prio number 1), but I think it is doable by changing the default workflow. 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: custom group for ticket permission
2008/10/8 Jani Tiainen [EMAIL PROTECTED]: Doesn't that BlackMagicTicketPlugin make possible to create arbitary permissions for tickets? Side note: Does it really enforce permissions or does it rather make fields un-editable via Genshi transformations? This is not the same. - Thomas --~--~-~--~~~---~--~~ 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: custom group for ticket permission
On Oct 8, 7:19 am, Jean Marie [EMAIL PROTECTED] wrote: First you need to create new permission, e.g. TICKET_CLOSE. How can i do this? I found an intermediate solution by hacking the database: INSERT INTO permission (username, action) VALUES (group_qa, TICKET_CLOSE); After this, the manuall added permissions assignment is visible in the admin section and also the trac-admin shows me this assignment. In trac.ini i've set: [ticket-workflow] close.permissions = TICKET_CLOSE Now only users that are members of group group_qa are able to close a ticket. For the moment this solution is fine by me. Are there any doubts about this solution? Maybe there'll be a more elegant way of adding user defined permissions. Best regards Jean Marie AHH, bad idea. stated about 3 responses up : And to create your own permissions : http://nil.checksite.co.uk/post.cfm/trac-0-11-creating-your-own-permissions again, note his code isn't formatted properly for python on that web site. in this thread: http://groups.google.com/group/trac-users/browse_thread/thread/79b11813a0cd25ab/e1710f4f7dc76cf3?hl=enlnk=gstq=custom+permissions#e1710f4f7dc76cf3 I posted a copy of it, which should be formatted. however, it is a google email group, so ymmv create that python file (modified for your permission(s) , drop it in your plugins directory, restart your server, and you should be good to go. you may need to enable the plugin in the web admin, I forget. additionally, you MAY want to take a look at the enterprise-workflow in the contrib directory, which has a resloved-verfied type workflow, plus a special ticket handler to prevent the person that resolved a ticket from verifying it. Maybe combine the 2. we implement a custom workflow with resolved-verified. but we don't enforce who verifies, since this step is basically author testing/ verification it was merged into the trunk. we have a separate qa step that tests irrespective of tickets. --~--~-~--~~~---~--~~ 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: custom group for ticket permission
Hi, On 7 Okt., 15:48, Rainer Sokoll [EMAIL PROTECTED] wrote: Maybehttp://trac-hacks.org/wiki/BlackMagicTicketTweaksPluginis what you are looking for? i already use BlackMagicTicketTweaksPluginis for customizing the appearance of certain ticket fields. It also provides to permit a field from being changed by non-priviliged users. But that's not what i want. I want to disallow a group of user to select a certain action for a ticket, e.g. a developer is not allowed to close a ticket. Anyway, thanks for your answer. Best regards Jean Marie --~--~-~--~~~---~--~~ 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: s5 plugin and 0.11 patch (generaly plugin-patch question acutally)
On Oct 6, 4:41 pm, Stephen Moretti [EMAIL PROTECTED] wrote: 2008/10/6 [EMAIL PROTECTED] Just an idiot question here. How do I correctly apply this patch? So I get the plugin source, apply the patch, then bake an egg? Or do I install the egg, then apply the patch. I am going to assume: check out plugin source, apply patch, bake egg, install. Might be nice to just create a 0.11 branch of this plugin. Checkout the source, apply the patch and use easy_install to install the egg. Which plugin? -- Stephen Moretti Blog :http://nil.checksite.co.uk/ Twitter :http://twitter.com/mr_nil thanks, I actually just pulled the oforge guys' fork of it, which is updated for 0.11 the plugin I was referring to, is the s5 plugin, hence the title. --~--~-~--~~~---~--~~ 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: custom group for ticket permission
2008/10/8 Jani Tiainen [EMAIL PROTECTED] Rainer Sokoll kirjoitti: On Wed, Oct 08, 2008 at 01:59:48AM -0700, Jean Marie wrote: I want to disallow a group of user to select a certain action for a ticket, e.g. a developer is not allowed to close a ticket. I have a similar issue. A developer must not close a ticket, instead, once he marked a ticket resolved, the ticket must go over to the QA people. They will perform their tests and finally, either close the ticket or re-assign it to the developer. This is still not resolved for me (has not prio number 1), but I think it is doable by changing the default workflow. Correct. First you need to create new permission, e.g. TICKET_CLOSE. And to create your own permissions : http://nil.checksite.co.uk/post.cfm/trac-0-11-creating-your-own-permissions Please note the comment by PythonGuy about formating... I still need to get around sorting out the code display on my blog :/ --~--~-~--~~~---~--~~ 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: custom group for ticket permission
Hi, On 7 Okt., 15:48, Rainer Sokoll [EMAIL PROTECTED] wrote: Maybehttp://trac-hacks.org/wiki/BlackMagicTicketTweaksPluginis what you are looking for? i already use BlackMagicTicketTweaksPluginis for customizing the appearance of certain ticket fields. It also provides to permit a field from being changed by non-priviliged users. But that's not what i want. I want to disallow a group of user to select a certain action for a ticket, e.g. a developer is not allowed to close a ticket. Anyway, thanks for your answer. Best regards Jean Marie --~--~-~--~~~---~--~~ 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: How can I configure Trac to use subversion 1.5
On Wed, Oct 08, 2008 at 05:36:50AM -0400, Robert C Corsaro wrote: Out of curiosity, what do you expect to get from running 1.5 on the server side? Merge tracking is what my users were emphatically asking for. 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: how is trac SUPPOSED to be used?
well, out of the box, trac does have a usage workflow. new-assigned- closed if you are after something a little more common try the enterprise workflow in the contrib directory. that said, it sounds like your group is perfectly happy being stuck with something that is not customizable (or easily customized). in that case, you might consider something else, but with the caveat that nobody gets to ask for customizations (maybe aside from themes/skins) Trac is a bit of labor to get it tweaked to exactly what fits your organization. The flip side, is, well, it's worth it because you CAN if you're agile, you could look at agilo. there is a release candidate that runs on 0.11 and looks very complete. Even this still allows a ALOT of customization, which I find a good thing, but out of the box, it's good to go. in order to do your date searching you mentioned, you will need to write sql. there are some examples around on how to get this, so you really only need to find it and cut and paste into a query. (sorry I don't have a link atm, but I found one a while back that finds when a ticket TRANSITIONED to closed, which was perfect) however, another option is to add the DateTime plugin, and add a custom field to tickets which people are required to fill in with the current date when they close a ticket. Or you use more milestones, and assign ticket to the milestone for the last to weeks. if it's closed, and milestone matches...etc. this would be more towards the sprint model of scrum. I will go back to say, I bet even with an out of the box solution, your group will want SOME sort of customization, which might be difficult if not impossible with other systems. (such as custom workflows, particularly to the level Trac has them.) The subversion hooks are really nice as well. the ability to update a ticket when you check in a file, just via the comments, adds to productivity and traceability. This again, is something you need to enable/configure, since trac doesn't force you to even use source control at all. Still sounds like the best route for you personally might be somehting else that is out of the box, and inflexible. and then they are just stuck with 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: how is trac SUPPOSED to be used?
Chad Emahizer wrote: I think I might be restating a bit here from what others have already said, but Trac does (or can do) what you want it to do. It is flexible and doesn't force its own business logic on its users. It basically has to be like that, or it will be targeting only a small portion of the population regardless of whichever specific implementation it would choose to implement. A problem with that approach is that not only do you have to learn a new tool, but you also have to understand the processes your company has in place and then determine ways to configure/utilize Trac to fit in with those processes. ... So, maybe the question shouldn't be How is Trac supposed to be used?. Maybe it should be What are the processes for my company, and how can I tailor Trac to enforce those processes and make them easier to do? There are 2 kinds of users: those who want to tweak software to do what they want, and those who're happy to click on a button and let the software take them to wherever Bill Jobs (aka Steve Gates) thinks they want to go. Those in the second category should probably not use trac, linux, or any programming languages other than flash. Dima --~--~-~--~~~---~--~~ 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: how is trac SUPPOSED to be used?
Dimitri Maziuk wrote: Chad Emahizer wrote: I think I might be restating a bit here from what others have already said, but Trac does (or can do) what you want it to do. It is flexible and doesn't force its own business logic on its users. It basically has to be like that, or it will be targeting only a small portion of the population regardless of whichever specific implementation it would choose to implement. A problem with that approach is that not only do you have to learn a new tool, but you also have to understand the processes your company has in place and then determine ways to configure/utilize Trac to fit in with those processes. ... So, maybe the question shouldn't be How is Trac supposed to be used?. Maybe it should be What are the processes for my company, and how can I tailor Trac to enforce those processes and make them easier to do? There are 2 kinds of users: those who want to tweak software to do what they want, and those who're happy to click on a button and let the software take them to wherever Bill Jobs (aka Steve Gates) thinks they want to go. Those in the second category should probably not use trac, linux, or any programming languages other than flash. Dima Man, you're not supposed to say stuff like that out loud. That's why everyone hates us! --~--~-~--~~~---~--~~ 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: how is trac SUPPOSED to be used?
Robert C Corsaro wrote: Man, you're not supposed to say stuff like that out loud. That's why everyone hates us! Not everyone, just the second bunch -- us arrogant elitists snobs generally don't have a problem with the idea that trac is not right for everyone. It's the other crowd that tends to fervently believe what's good enough for them must be good enough for jesus and the rest of human species -- and you better like it! Dima --~--~-~--~~~---~--~~ 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: how is trac SUPPOSED to be used?
On Wed, Oct 08, 2008 at 08:21:42AM -0400, Chad Emahizer wrote: I broke this out into a separate email because otherwise it would be one huge email that rambled, which I have a tendency to do anyway... I might try to do this specific example with milestones. Define a Trac milestone as a merge point in the software, like the one you had two weeks ago. Assign the tickets to the next milestone in line, and when a merge point happens, create another milestone and send all unresolved tickets to that new milestone. At any given time you can quickly see what tickets have been closed by milestone. I wouldn't exactly say that's how I would use the milestone feature in a perfect world (I like to at least of the pretense of planning), but it would likely work used that way. snip/ As far as how trac is supposed to be use with respect to those that want a program to enforce methodology versus a program to support multiple methodologies, it seems to me that using milestones is the trac way of doing what is desired here. Marking things as milestones is probably a good practice anyway for this case as it enables a project manager to think of a group of tickets as a concerted effort instead of the more ad hoc date query. IMHO, Jeff Hammel The Open Planning Project http://topp.openplans.org IRC: jhammel, k0s Another approach could be to use the version field. Make set the version field up to have whatever you want to call the merge points, like the one you had two weeks ago. Code name them. Refer to a build number. Use a targeted merge date...whatever. As you close tickets, set the version to the merge point next in line when it was closed. This isn't exactly right either, as Version would typically (I think) be used to designate what software version the issue was found in, not the version the issue would be fixed in. However, that being said, you are free to use it how you like and define. A third could be a custom field. Make a custom field for whatever you want to call the merge points as said above. As you close tickets, set the field to the name of the merge point next in line when it was closed. This approach is a little harder because querying based on custom fields is tough, or so I have read...I've not done it. I'm fairly confident, as you pointed out, that if I decided I needed to search custom fields for something I could find adequate documentation to help me do so, I've just not had the need. Hope I was at least a little helpful. Chad -Original Message- From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Stedwick Sent: Tuesday, October 07, 2008 3:38 PM To: Trac Users Subject: [Trac] how is trac SUPPOSED to be used? For example, my boss recently asked me what changes were going to be moved into the trunk since the last merge two weeks ago, and I thought to myself, Oh, I'll just do a search for all the bugs that I fixed in the past two weeks, but, amazingly, I CAN'T DO THAT. Even using custom query there is no field that allows you to query based on time. And I certainly don't want to start writing SQL. --~--~-~--~~~---~--~~ 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: how is trac SUPPOSED to be used?
On Wed, Oct 08, 2008 at 08:46:48AM -0400, Chad Emahizer wrote: Could there possibly be a way to develop and distribute specific configurations of the trac.ini file and a trac.db file? Maybe it's as simple as that. I would think some sort of white paper would be needed (maybe documented in the wiki) that explains how the specific process the specific configuration is supposed to work. Maybe a large(ish) percentage of processes could be covered by a small(ish) number of specific implementations. I think it is akin to how Apache and mysql was for me when I was trying to install a certain web-based bug tracking system for the first time. I didn't know how to run a web server and deal with a db server. More importantly, I didn't want to learn...had neither the time nor the desire. So finding the prebuilt and configured Apache release XAMPP by Apache Friends was the only thing that allowed me to move forward. Is it as simple as defining and documenting a process, configuring it, zipping the necessary pieces, and putting it up for distribution? Ok, not so simple to define said process, but configuring Trac once the hard part is done is relatively easy I think. It would be nice to have certain plugins preinstalled too, though I'm sure there's issues with redistributing others' plugins, even with the positive goal of more adoption of Trac. I've not tinkered with dropping portions of a configured Trac system into an existing Track install to see how it reacts... This would allow the ability for Trac development to continue on the generic path it is currently on, yet allow someone to pick a pre-setup configuration that more closely fits the way they do business so they don't have to get their hands dirty in the nitty-gritty details. This IMHO is the right direction to go: keep trac generic but allow people ways of easily distributing customized packages that can be used to create trac instances. To this end, I've been working on a program called TracLegos (http://trac-hacks.org/wiki/TracLegosScript) that will do just that -- allow packaging and distribution of trac.ini files and requirements files for plugins. The program is still in its infancy, but I'd love feedback on whether this idea is useful to people. It was motivated by this concern coming up again and again. (Nor is TracLegos the only software that does this. TracForge also supports this sort of thing) Hope this is useful, at least in the abstract. Feel free to ticket and ask questions, as I'm very interested in people using this plugin if it does help with this problem. Jeff Hammel The Open Planning Project http://topp.openplans.org IRC: jhammel, k0s -Original Message- From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Noah Kantrowitz Sent: Wednesday, October 08, 2008 3:20 AM To: trac-users@googlegroups.com Subject: [Trac] Re: how is trac SUPPOSED to be used? This is correct, one of the central design tenets of Trac is that it enforces as little process on you as possible. This does seem to backfire sometimes, as there is a large segment of the userbase that would like more structure than that. If you have a suggestion on how to resolve this, please let us know, it is frequently debated but people rarely seem to come up with anything solid. --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: how is trac SUPPOSED to be used?
On Tue, Oct 7, 2008 at 3:37 PM, Stedwick [EMAIL PROTECTED] wrote: I'm wondering if it's a philosophical conflict. The people at my company (myself included) like opinionated software. It's like iTunes. Everybody hates iTunes because they can't manage their music in their own unbelievably specific manner. However, if you use iTunes as it was DESIGNED to be used, you will discover that it's an amazing, excellent piece of software. I can't imagine managing my music any other way. It just works so well. You just have to get by the fact that you have to do things the Apple way. Believe it or not, the Apple way is usually pretty good. Perhaps that's it. I think the Apple way is awful, and nowhere near what I want. The very *least* iTunes could do is let me enter a format string for how I want files named when I rip a CD, but it can't even do that. But that aside, I'm not sure how else to understand your dilemma with Trac. If you want Trac to dictate how you do your work you could try one of the more structured derivatives like Agilo. But it really depends on what your development process is. You said it yourself--Trac is meant to stay out of the way and mostly only do what you want it to do. If you don't even know what you want to do with it, I can understand how you're stuck. --~--~-~--~~~---~--~~ 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: how is trac SUPPOSED to be used?
On Wed, Oct 8, 2008 at 10:45 AM, Robert C Corsaro [EMAIL PROTECTED] wrote: Dimitri Maziuk wrote: Chad Emahizer wrote: I think I might be restating a bit here from what others have already said, but Trac does (or can do) what you want it to do. It is flexible and doesn't force its own business logic on its users. It basically has to be like that, or it will be targeting only a small portion of the population regardless of whichever specific implementation it would choose to implement. A problem with that approach is that not only do you have to learn a new tool, but you also have to understand the processes your company has in place and then determine ways to configure/utilize Trac to fit in with those processes. ... So, maybe the question shouldn't be How is Trac supposed to be used?. Maybe it should be What are the processes for my company, and how can I tailor Trac to enforce those processes and make them easier to do? There are 2 kinds of users: those who want to tweak software to do what they want, and those who're happy to click on a button and let the software take them to wherever Bill Jobs (aka Steve Gates) thinks they want to go. Those in the second category should probably not use trac, linux, or any programming languages other than flash. In fairness to Bill Gates, I've found most Microsoft software much more willing to be told to behave the way I want it to behave than Apple software. That's not to say that the MS stuff doesn't have its own set of usability problems--it's usually clunkier and more bloated. I just usually feel far more boxed in when I'm using Apple software. But that's an off-topic discussion so I'll leave it at that. Now Trac, on the other hand, gives me a great deal of freedom. And of course as with any open source software (especially with a less restrictive license) we are free to modify it if there's something specific we need to change about it. And the fact that Trac imposes very little process to begin with, and is very modular, it's a lot easier to modify without stepping on any toes. --~--~-~--~~~---~--~~ 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: MultipleRepositorySupport install error
On Oct 6, 5:39 pm, Stephen Moretti [EMAIL PROTECTED] wrote: I'm running the multirepo install on windows with svn without any problems. Sounds like you've got a setting wrong somewhere. I think I had the same problem initially, but a quick RTFM solved it. Did you previously have a standard installation of Trac with hg running? I tried the single repository version but that failed also similarly Did you do a search on the trac website for your error message?http://trac.edgewall.org/ticket/7346 Yes however I did not find the above link. Thanks for sending that. The python check that worked for me was $ python Python 2.4.3 (#1, Oct 23 2006, 14:19:47) [GCC 4.1.1 20060525 (Red Hat 4.1.1-1)] on linux2 Type help, copyright, credits or license for more information. import mercurial When I tried some of the python tests in the above ticket link they failed however I am not sure if the failed ones were applicable to my version of trac. An example one that failed was: import backend Traceback (most recent call last): File stdin, line 1, in ? ImportError: No module named backend Have you confirmed that you've got the correct Mercurial Plugin installed?http://trac.edgewall.org/wiki/TracMercurial Yes I was able to view the administrative pages as TracAdmin and saw that the correct plugin was installed. Stephen --~--~-~--~~~---~--~~ 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: Need help on Change History Trac
Hi Noah, Thanks a million for your impulse response. I got a response from Christian Boss. Wanted to share with you. Also I'm a newbie to trac. Can you please elaborate How to put JS hackery in the ticket.html template. Here is the mail from Christian Boss. *** Hello Damodharan, Kuttiyappan, Damodharan (CONTRACTOR) wrote: Hi Christian Boos, I'm Damodharan Kuttiyappan, working as a Configuration Manager in ATX Group Inc, Texas. We are evaluating Trac Integrated SCM and Project Management for our Bug tracking purpose. It's an excellent open source tool for bug tracking. I would like to implement few features on Trac. Our first target is to add a button next to Change History (Show/Hide button). When we click on the button, it should show the change history log. By default we want to make the changes log as an hidden think as the Trac users feel Change history occupies most of the pages when the bugs have been transferred between users. That's a similar request to a recently posted ticket, see http://trac.edgewall.org/ticket/7639 and http://trac.edgewall.org/ticket/7640 I need your advise to implement this change. Help me to locate the file where do I need to make the changes. I'm looking forward to your reply. Well, I'm afraid I can't help directly right now, but there are plenty of good guys willing to help for such topics on the Trac mailing lists http://trac.edgewall.org/wiki/MailingList ;-) One hint would be to look at the existing hide/show code we have in the custom query views (trac/ticket/query.py and trac/ticket/template/query.html). Hope this helps, -- Christian *** Thanks, Damodharan -Original Message- From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Noah Kantrowitz Sent: Wednesday, October 08, 2008 2:21 AM To: trac-users@googlegroups.com Subject: [Trac] Re: Need help on Change History Trac You could probably put some JS hackery in the ticket.html template. Doing this right would entail making a plugin to add the JS to the ticket page and possibly setting up a stream filter for fallback. --Noah On Oct 7, 2008, at 12:43 PM, Damu wrote: Trac Users, I'm Damodharan Kuttiyappan, working as a Configuration Manager in ATX Group Inc, Texas. We are evaluating Trac Integrated SCM and Project Management for our Bug tracking purpose. It's an excellent open source tool for bug tracking. I would like to implement few features on Trac. Our first target is to add a button next to Change History (Show/Hide button). When we click on the button, it should show the change history log. By default we want to make the changes log as an hidden think as the Trac users feel Change history occupies most of the pages when the bugs have been transferred between users. I need your advise to implement this change. Help me to locate the file where do I need to make the changes. I'm looking forward to your reply. Thanks, Damodharan. --~--~-~--~~~---~--~~ 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: How can I configure Trac to use subversion 1.5
On Oct 8, 4:17 am, Rainer Sokoll [EMAIL PROTECTED] wrote: On Tue, Oct 07, 2008 at 05:18:49PM -0700, [EMAIL PROTECTED] wrote: I am running on ubuntu. How can I get the python subversion 1.5 binding? The package manager (atitute) only has 1.4.x binding. Use the sources. It is fairly easy to build one's own subversion and SWIG bindings. Rainer Rainer, This is what I have been trying to do. But I can't get it to work. I am trying to compile subversion python binding in subversion 1.5.2 on ubuntu. So I get the source of neon, apr and apr-util and put it under subversion 1.5.2. And then I do $ ./configure --prefix=/home/meryl/bin --with-swig=/home/meryl/bin -- with-ssl $ make $ make install $ make swig-py $ make install-swig-py And then I set the pythonpath correctly: echo $PYTHONPATH /home/meryl/bin/lib/svn-python But when i do a test (like below), i get the following error: $ python -c 'from svn import client' Traceback (most recent call last): File string, line 1, in module File /home/scheung/bin/lib/svn-python/svn/client.py, line 19, in module from libsvn.client import * File /home/scheung/bin/lib/svn-python/libsvn/client.py, line 7, in module import _client ImportError: /home/scheung/bin/lib/libsvn_ra_neon-1.so.0: undefined symbol: GENERAL_NAME_free And I have done 'ldd' of the 'libsvn_ra_neon-1.so.0' and check LD_LIBRARY_PATH is set correctly. $ ldd /home/meryl/bin/lib/libsvn_ra_neon-1.so.0 linux-gate.so.1 = (0xb7f46000) libsvn_delta-1.so.0 = /home/meryl/bin/lib/libsvn_delta-1.so.0 (0xb7efe000) libsvn_subr-1.so.0 = /home/meryl/bin/lib/libsvn_subr-1.so.0 (0xb7ec6000) libaprutil-0.so.0 = /home/meryl/bin/lib/libaprutil-0.so.0 (0xb7eb) libexpat.so.1 = /usr/lib/libexpat.so.1 (0xb7e8f000) libapr-0.so.0 = /home/meryl/bin/lib/libapr-0.so.0 (0xb7e6d000) librt.so.1 = /lib/tls/i686/cmov/librt.so.1 (0xb7e64000) libm.so.6 = /lib/tls/i686/cmov/libm.so.6 (0xb7e3f000) libcrypt.so.1 = /lib/tls/i686/cmov/libcrypt.so.1 (0xb7e0c000) libnsl.so.1 = /lib/tls/i686/cmov/libnsl.so.1 (0xb7df4000) libpthread.so.0 = /lib/tls/i686/cmov/libpthread.so.0 (0xb7ddc000) libdl.so.2 = /lib/tls/i686/cmov/libdl.so.2 (0xb7dd8000) libc.so.6 = /lib/tls/i686/cmov/libc.so.6 (0xb7c89000) libz.so.1 = /usr/lib/libz.so.1 (0xb7c74000) /lib/ld-linux.so.2 (0xb7f47000) [EMAIL PROTECTED]:~/src/swig-1.3.36$ echo $LD_LIBRARY_PATH /home/meryl/bin/lib::/usr/lib:/usr/local/lib:/lib/tls/i686/cmov:/lib: Can you please help me why? Thank 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: How can I configure Trac to use subversion 1.5
On Wed, Oct 08, 2008 at 10:29:34AM -0700, [EMAIL PROTECTED] wrote: But when i do a test (like below), i get the following error: $ python -c 'from svn import client' Traceback (most recent call last): File string, line 1, in module File /home/scheung/bin/lib/svn-python/svn/client.py, line 19, in module from libsvn.client import * File /home/scheung/bin/lib/svn-python/libsvn/client.py, line 7, in [...] $ ldd /home/meryl/bin/lib/libsvn_ra_neon-1.so.0 scheung != meryl :-) 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?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Looking for the record creator
On Oct 8, 8:53 am, Noah Kantrowitz [EMAIL PROTECTED] wrote: On Oct 7, 2008, at 11:51 PM, didley wrote: On Oct 7, 9:33 am, Stephen Moretti [EMAIL PROTECTED] wrote: 2008/10/7 didley [EMAIL PROTECTED] Sometimes it's necessary that a user with ticket-admin permission has to create tickets with to fill out reporter and assign a owner. When this is done I can't see the creator (ticket-admin) of the ticket. After a while all user thinking the inscribed reporter is the creator but it isn't. Is there a field in the table schema of trac where I can find the creator? Nope. The reporter is the creator under most circumstances. Have you thought of leaving the reporter as the ticket-admin and adding the person who emailed/called the ticket as a cc member? Or possibly adding a custom field for the creatpr? Stephen That's pity. I have to think obout if add a custom field for it. I suppose it's the only way I have. It would be pretty easy to automate in a plugin, just make an ITicketManipulator that sets the field value on create to req.authname. --Noah- Hide quoted text - - Show quoted text - I would if I could. didley --~--~-~--~~~---~--~~ 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: Looking for the record creator
from trac.core import * from trac.ticket.api import ITicketManipulator class SetCreatorModule(Component): implements(ITicketManipulator) def prepare_ticket(self, req, ticket, fields, actions): pass def validate_ticket(self, req, ticket): if req.path_info == '/newticket': ticket['creator'] = req.authname return () -Original Message- From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of didley Sent: Wednesday, October 08, 2008 11:40 AM To: Trac Users Subject: [Trac] Re: Looking for the record creator On Oct 8, 8:53 am, Noah Kantrowitz [EMAIL PROTECTED] wrote: On Oct 7, 2008, at 11:51 PM, didley wrote: On Oct 7, 9:33 am, Stephen Moretti [EMAIL PROTECTED] wrote: 2008/10/7 didley [EMAIL PROTECTED] Sometimes it's necessary that a user with ticket-admin permission has to create tickets with to fill out reporter and assign a owner. When this is done I can't see the creator (ticket-admin) of the ticket. After a while all user thinking the inscribed reporter is the creator but it isn't. Is there a field in the table schema of trac where I can find the creator? Nope. The reporter is the creator under most circumstances. Have you thought of leaving the reporter as the ticket-admin and adding the person who emailed/called the ticket as a cc member? Or possibly adding a custom field for the creatpr? Stephen That's pity. I have to think obout if add a custom field for it. I suppose it's the only way I have. It would be pretty easy to automate in a plugin, just make an ITicketManipulator that sets the field value on create to req.authname. --Noah- Hide quoted text - - Show quoted text - I would if I could. didley --~--~-~--~~~---~--~~ 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: Customizing Trac
On Oct 7, 11:45 am, W. Craig Trader [EMAIL PROTECTED] wrote: Thanks for the reply. Don't assume that '4 hours' was spent only on this task. I wrote my reply so that everyone would know that I solved my problem, but that was the last thing I did that day. Yeah, it would have been helpful if I had spotted the BlackMagicTweaks plugin -- it does everything I wanted, and I may use it in the future. It would have been MORE helpful if any of the searching I did prior to diving into the source had pointed to this specific plugin, say, somewhere on the Trac Wiki under customizations. I love the flexibility of Trac, but that flexibility comes at the cost of complexity. - Craig - Four hours and apparently? Wouldhttp://www.trac-hacks.org/wiki/BlackMagicTicketTweaksPlugindo some of what you're needing? Sorry about that. I agree with what you say. Trac looks very enticing but it can be quite difficult to work out how to use it and get it to do what you need. --~--~-~--~~~---~--~~ 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] trouble saving new pages
Using Trac 0.11.1 and sqlite. When I create a new page and enter some text, then save it, the page is not saved. If i hit the back button and _then_ save all is well. This happens mostly with new pages but also occasionally with edits to existing pages. Anyone have any ideas? I've checked permissions but I _can_ save pages, just not the first time. --~--~-~--~~~---~--~~ 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: s5 plugin and 0.11 patch (generaly plugin-patch question acutally)
On Wed, Oct 8, 2008 at 6:38 AM, [EMAIL PROTECTED] wrote: On Oct 6, 4:41 pm, Stephen Moretti [EMAIL PROTECTED] wrote: 2008/10/6 [EMAIL PROTECTED] Just an idiot question here. How do I correctly apply this patch? So I get the plugin source, apply the patch, then bake an egg? Or do I install the egg, then apply the patch. I am going to assume: check out plugin source, apply patch, bake egg, install. Might be nice to just create a 0.11 branch of this plugin. Checkout the source, apply the patch and use easy_install to install the egg. Which plugin? -- Stephen Moretti Blog :http://nil.checksite.co.uk/ Twitter :http://twitter.com/mr_nil thanks, I actually just pulled the oforge guys' fork of it, which is updated for 0.11 the plugin I was referring to, is the s5 plugin, hence the title. any chance trac-hacks getting updated for 0.11 ? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
