bug-tracking

I use trac to manage my projects and I'd like to organize wiki pages the same way trac project does, i.e. by category, subcategory, etc. TitleIndex page on trac site gives a good explanation of the result I want to obtain. How do I achieve this? First of all, you can create hierarchically wiki pages, just by modifying the url, and press enter. It is also possible to create a wikilink first, and then press the red link. For example, when your trac home page is http://trac.server.local/project/wiki , you can type /customers at the end of the url, and press enter. So the new url would be http:/

I found a lot of questions asking for the best tool, but none asking for the features, you really need ? And what features you never really needed? (I caught myself to be comparing tools on feature matrices. Something I hate, because in the end I will be using only the 3-4 most important features and leave the rest untouched.) It need to: collect bugs order bugs on priority/severity/due date etc assign bugs to developers track a bug history link similar bugs together link bugs to customers link solved bugs to releases provide enough information or a reference to get the information to

I know about Fossil but are there any alternatives? Something small and easy to install/configure. I know there are quite a few git-based wikis such as git-wiki , WiGit and gitit . A simple google search will bring up many others, I'm sure. I also know of some git-based bug trackers such as ticgit which basically lets you keep your tickets in a separate branch of a git repository. There's also DisTract . But I'm not aware of anything else aside from Fossil that really tries to do what it does in one combined tool. I'm curious what your experiences with Fossil have been. It's one of those

What do you think about TFS as time tracking tool? Are there built-in functionalities that can efficiently track time that is spent at some work items, sprints, projects,... Also, it would be useful to explain how to do it. I found at MSDN forum some suggestions that it is better to use some other tool. What is your opinion about this? I edited this post, because I wanted to add one more topic - Bug tracking. During internet search I found many articles that agree that TFS is good Bug tracking tool, so I wanted to ask for your experiences and for suggestion for good How-to articles or books.

Is there an equivalent to Trac written in PHP? I need something that integrates with SVN and is free. It should allow me to browse the SVN source, have some kind of bug tracking and show recent changes in the SVN. A wiki isn't essential. Thanks in advance. 来源： https://stackoverflow.com/questions/349241/is-there-an-equivalent-to-trac-written-in-php

Is there any good bug tracker based on .NET which is free? Two bug trackers I know: BugTracker.NET BugTracker.NET is a free, open-source, web-based bug tracker or customer support issue tracker written using ASP.NET, C#, and Microsoft SQL Server (or its free cousin, SQL Server Express). BugNET BugNET is an issue tracking and project issue management solution built using the ASP.NET web application framework. Email notifications, reporting and per project configuration of fields and values allows efficient management of bugs, feature requests, and other issues for projects of any scale.

In the past I have really enjoyed using Trac with subversion repositories hosted on some of my own servers. The integrated ticketing and online code browsing is very convenient. I have used github for some of my public projects but I don't have the money to shell out for an extra service, espcially when I am already paying for remote VPS hosting. Does anyone know of or have any experience setting up something like Trac with git version control? Specifically, I can already push to a remote server but I would like some web interface that allows me (and people working with me) to see that commits

There seems to be a bug with the Windows 7 batch file 'for' command. This command can walk through a source directory and return one filename at a time. But I found that if my command modify the files in that source directory e.g. for /R %1 %%s in (*.*) do call :do1file %%s @goto :EOF :do1file @echo es > tmp_x2932.tmp move /y tmp_x2932.tmp %1 @goto :EOF the 'for' command could invoke the do command with the same file name more than 1 times. (Note that, for the purpose of illustrating the issue, the 'echo es > tmp_x2932.tmp' is just a simple replacement of some other legitimate command, like