bgcolor # Type Status Created By Changed Assigned Svr Pri Title Opis #e8e8bd 90 new active 2002 Aug anonymous 2002 Aug drh 3 2 Handle different projects in one CVSROOT When more than one project is located under one CVSROOT it is difficult (or impossible) to create an Milestone for an special project. Remark: Yes, I know how to it from the command line. #cacae5 99 new active 2002 Aug anonymous 2002 Aug 4 4 Cvstrac home or index page not found when project is omitted Cvstrac displays this error page when no project is included in the request URL: ----- *Not Found* Page not found: / ----- We installed cvstrac as a CGI script in the admin directory of our web server. Cvstrac responds correctly to requests like /admin/cvstrac/project1 and /admin/cvstrac/project2. When passed the request /admin/cvstrac it displays the error page. I recommend that cvstrac respond with either an index of available projects or a static HTML page. #cacae5 158 new active 2002 Dec anonymous 2002 Dec drh 4 4 Make ticket page a Wiki page with generalised meta-formatting If the Wiki supported keywords like {SQL: command }, then it would be possible to create Wiki pages that interface with the database. In this scheme, a ticket page might be written in the Wiki like (I don't know any SQL yet): Ticket {SQL: ITEM.number }: ticket dependencies and estimated duration {SQL: ITEM.description } Remarks: {SQL: ITEM.remarks } And editing the page will bring up edit blocks which feed the data back into the database, like the Create New Ticket page. The same idea could apply to reports, so the generated report page could also have an "edit" tag, which brings up the same information in edit blocks for editing the database contents. This would let me perform tasks like create a report for all entries older than 4 weeks along with their priority levels, click [Edit] and directly modify all their priority levels. This would mean that Ticket pages are just Wiki pages with meta structural information, and all Wiki pages can extract and modify SQL database information. This scheme also handles the scenario in the TODO item: * Text above ==== may only be editted by the document owner #cacae5 178 event active 2003 Feb anonymous 2003 Feb drh 3 4 Old or legacy rcs (not sure) is unable to handle 'date <= date' Import of CVS history generates loads of errors: No revision information found in rlog output: rlog '-d1999-06-01 13:48:14<=2003-02-12 09:21:14' '/daily/CVSROOT/CVSROOT/loginfo,v' 2>/dev/null; Runnin rlog manually, I got: rlog error: can't parse date/time: =2003-02-12 09:21:14 rlog aborted Modifying '<=' to '<' at the appropriate line in history.c solves the problem for me. Not sure if it's suitable as general solution. #cacae5 175 new new 2003 Feb anonymous 2003 Feb drh 3 4 A second CVSTrac logs out the first one. I use CVSTrac for two projects. I usually have two browser tabs open, each showing the CVSTrac timeline for one of the projects. After I've logged in for the second CVSTrac, the a refresh on the first one goes to the login page. Logging in again for the first one causes the second one to be logged out. It would be nice if I could be logged in on both projects simultaneously (some cookie manipulation required?). #cfe8bd 180 new active 2003 Feb anonymous 2003 Feb drh 3 3 Larger text fields in ticket editor I'd like to be able to set, perhaps in the setup page, the number of lines for the description and remarks fields. #cfe8bd 181 event active 2003 Feb anonymous 2003 Feb drh 3 3 No in ticket editor In tktedit, there are tags between all the popup menus and fields (status, type,...,contact). I'd like these to be removed so that I don't have to make the browser window really wide to see them all. ---- I'm having the most trouble with Safari (Apple's new KHTML browser). Even though the Associated Check-ins text field is 70 wide (why?), it never wants to put a break before it. The W3C Validator said that was invalid. When I remove those tags, it renders fine in Safari. I can attach some screenshots if you want, but for some reason it's not letting me (even thought it said I would be given the opportunity to add one when I created the ticket). #f2dcdc 191 event active 2003 Mar anonymous 2003 Mar drh 3 1 User keeps getting logged out One of my developers keeps getting logged out. He says a typical session goes like this: Yip. Cookies enabled. I just tried it under netscape as well. 1) Login 2) Wiki 3) edit (or was it note, edit?) 4) Now logged in as anon. not Andre Same thing happens with making or editing tickets. #cacae5 210 new active 2003 Apr anonymous 2003 Apr 3 4 what about numbers in CamelCase words ? I'm starting to use Wiki on a project and I need to create pages with numbers in name (i.e. SubProj101, SubProj102 etc.).{linebreak} The name is not converted to hyperlink, it appears as the presence of digits violates the coding, but unfortunately a lot of names (especially technical-related) use digits. it could be enough to make a little change in format.c: = Actual = int is_wiki_name(const char *z){ int i; int nCap = 0; if( !isupper(z[0]) ) return 0; for(i=0; z[i]; i++){ if( isupper(z[i]) ){ if( !islower(z[i+1]) ) return 0; nCap++; }else if( !islower(z[i]) ){ break; } } return nCap>=2 && is_eow(&z[i],0) ? i : 0; } = Changed = int is_wiki_name(const char *z){ int i; int nCap = 0; if( !isupper(z[0]) ) return 0; for(i=0; z[i]; i++){ if( isupper(z[i]) ){ if( !(islower(z[i+1]) || isdigit(z[i+1]) ) ) return 0; // <<< nCap++; }else if( !islower(z[i]) ){ break; } } return nCap>=2 && is_eow(&z[i],0) ? i : 0; } Without changes in wiki_expand_name (wiki.c) the expansion will be: SubProj101 -> Sub Proj101, It should be acceptable.{linebreak} BTW: I included code fragments in 
 and
but it didn't worked. _Indent by two or more spaces to get verbatim text_ #cfe8bd 213 new active 2003 May anonymous 2003 May drh 5 3 Readying cvstrac for non-english alphabets The attached diff to cgi.c will allow use of danish and swedish (and probably all other) under netscape. #cfe8bd 164 doc active 2003 Jan anonymous 2003 Jun drh 5 3 Yet another multiple project per repository hack I've locally tweaked the 1.1.2 source code so that once read into a temporary 'fc' table, entries get deleted through an SQL query like 'DELETE FROM fc WHERE '. I've stored an SQL expression in the config table under the 'module_delete_where' identifier. Admitted, this is a quick and dirty hack but I definitely needed this feature as I have multiple projects sharing common modules in my unique repository. FYI, the hack is about 'setup.c' and 'history.c' files. The '.0' files are those of v1.1.2 release. Hope this helps. > diff -u setup.c.0 setup.c --- setup.c.0 2003-01-23 18:20:56.504453000 +0100 +++ setup.c 2003-01-21 17:32:42.468555000 +0100 @@ -117,6 +117,7 @@ }; const char *zRoot, *zOldRoot; const char *zModule, *zOldModule; + const char *zModuleDeleteWhere, *zOldModuleDeleteWhere; /* The user must be the setup user in order to see ** this screen. @@ -155,6 +156,21 @@ } /* + ** The "x" query parameter is the expression matching the name - + ** actually what shall not be deleted - of the module within the + ** CVS repository that this CVSTrac instance is suppose to track. + ** Change it if it has changed. + */ + zOldModuleDeleteWhere = db_config("module_delete_where",""); + zModuleDeleteWhere = P("x"); + if( zModuleDeleteWhere && strcmp(zOldModuleDeleteWhere,zModuleDeleteWhere)!=0 ){ + db_execute("REPLACE INTO config(name,value) VALUES('module_delete_where','%q');", + zModuleDeleteWhere); + zOldModuleDeleteWhere = zModuleDeleteWhere; + db_config(0,0); + } + + /* ** The "rrh" query parameter is present if the user presses the ** "Reread Revision History" button. This causes the CVSROOT/history ** file to be reread. Do this with caution as it erases any edits @@ -219,15 +235,23 @@ @ (for example, if you want CVSTrac to see only one module in a @ repository that contains many unrelated modules) then @ enter a pathname prefix for the files you want to see in the - @ second entry box.

+ @ second entry box. If you want to ignore a subset of the files + @ contained in the CVS repository (for example, if you want CVSTrac to see + @ only some modules in a repository that contains many unrelated modules) + @ then enter an SQL expression of the modules to be filtered out while + @ parsing the history file.

@

@ @ - @ + @ @ @ @ - @ + @ + @ + @ + @ + @ @ @
CVS repository:
Module prefix:
Module 'delete where' expression:

@ > diff -u history.c.0 history.c --- history.c.0 2003-01-23 18:21:06.814517000 +0100 +++ history.c 2003-01-21 14:02:56.432465000 +0100 @@ -426,7 +426,20 @@ zModule ); } - + + /* + ** If the "module_delete_where" configuration parameter exists and is not + ** an empty string, then delete from the FC table all records dealing with + ** files that are not matching the fetched expression. + */ + zModule = db_config("module_delete_where", 0); + if( zModule && zModule[0] ){ + db_execute( + "DELETE FROM fc WHERE %s", + zModule + ); + } + /* ** Extract delta comments from all files that have changed. */ #cacae5 254 new active 2003 Oct anonymous 2003 Oct 5 4 Class & file names that look like CamelCase In our java development project, we often have docs and commit logs that refer to classes & source files that look like CamelCase -- e.g. ChangeLog, HashCache, MailTransferAgent. I've found myself clicking on these links in the vain hope they would take me to the source file or class in question. I'm wondering if you could have the CamelCase link directly to the source file; right now I usually click the link, and then edit the page to have a link to the relevant source file, but I like to use the "Contents" page to surf around, and I dont like having clutter in there. #cfe8bd 120 new active 2002 Sep anonymous 2003 Oct drh 4 3 make -j fails make -j fails with something _remotely_ similar to "I am too dumb to make page_index.h" To fix, apply this patch (uudecode and gunzip it) or change the "headers:" target in main.mk to "page_index.h headers:" (works with GNU make at least, not sure about BSD make though) begin 644 main.mk.diff.gz M'XL("'J>>CT"`VUA:6XN;6LN9&EF9@"-4<%2@S`4/).O>` M/;3>.RF$DH%`)PE6_]X\H"4P/<@A[^W.9H?LYJ(H@'9`511$$4@FFD!6A%)Z MWKT5;/D1'L/P$:)5$K\F3\]`0_MY>(7XOG^1KB=I&";Q.HGB04K2%&@4QOQ2MDLS8I13:M.H7K:0UGBRA;@\"]?U;[,A7]M2< MJ:SL%],=[31\>.;$CGA-],2RFX&<]824TQ="IS>$B_[. ;U+E+C/E*_O#F]F9EINVR2W_D#V*6"K)N`P`` ` end #cacae5 255 new active 2003 Oct anonymous 2003 Oct 5 4 Dumping javadocs into Wiki It would be nice to have a tool to dump javadocs (and I know Python has a similar system which would also benefit) into so your commit comments and wiki pages can easily link to that documentation. I'm not sure whether it would be better to change the parser to treat java.lang.String (and perl::CPAN, and the python version, etc.) as equivalent to JavaLangString, or to just add a suffix to the class names, like StringDoc; obviously the first would allow the javadocs themselves to be parsable as a wiki. The first is unappealing because of its language-specificness and so on, but of course its more "handy" for the users. The second could be done in anyway -- all you really need is a tool that allows you to add an arbitrary file as an arbitrary wiki page, and let the user write his own script to put which file where. Test text... #cacae5 263 event active 2003 Nov anonymous 2003 Nov drh 4 4 CGI problem with Opera browser I'm on a Linux system and use the latest Opera browser (version 7.21). I was trying to edit a page on the SQLite Wiki. When I clicked on "Preview Your Changes" I got the editing page back, not the preview. I tried the same thing on Mozilla. The preview worked fine. I submitted the edit and that worked fine too. Then, back in Opera, I went to the cvstrac wiki to create this ticket and had the same problem. Clicking on "Preview Your Changes" just brought the edit page back. Finally, I went back to Mozilla where I've been able to successfully create this ticket. #cacae5 179 new active 2003 Feb anonymous 2003 Nov drh 3 4 Making log message changes in the underlying ,v file Right now, editing the log message for a checkin from within CVSTrac does not modify the underlying CVS ,v files. To reflect any such changes in the underlying files manually is painful, since there may be multiple files in the checkin, and each could have a different revision number. It would be useful if CVSTrac could (as an option) modify the log message in the underlying ,v files (using the `cvs admin' command, or in some other way). #f2dcdc 294 doc active 2004 Mar anonymous 2004 Mar anonymous 1 1 Documentation on the CVS Repository CVSTRac doesnt recognize the CVS Repository even if you do a commit after an import. You must actually manually add each file like this cvs -d $CVSROOT add [file] then CVSTrac will display the CVS directory that this file resides in. #e8e8bd 299 new active 2004 Mar anonymous 2004 Mar drh 3 2 Add enums for severity and priority The numeric constants (1-5) for severity and priority are a source of confusions for our users - other systems that we have are using different numbering systems. It will help if the "enum" table will be extended to allow the assignment of labels to those levels. There is no need to change the actual coding - the 1-5 level are more than enough. The enums should be edited by the 'setup' user, and should be used for ticket entry and editing. #c8c8c8 302 new active 2004 Mar anonymous 2004 Mar drh 5 5 Allow queries to be embedded in other pages. It would be very useful to be able to add a tag to reports to include them in other pages. A combo box on the reports page could list destinations where the report could be embedded (ie: ticket page, milestone page, ticket edit page, home page, etc). By enabling select entries the user could embed the report in different pages. This could be used to provide a very simple mechanism to track dependancies. I have a report that lists all tickets that depend on a specified ticket (see attachment). By embedding this query in the ticket overview page I could follow a link to any dependent tickets. A similar report on the milestones page would allow all tickets that depend on a milestone to be listed. It might be useful to embed the "Ticket Counts" report on the main page. etc. One issue I don't know how to resolve would be passing the page identifier to the query. Each embedding location could define a key (or keys) it would make available to the query, but I don't know how it would be incorporated into the query. I assume something similar to the aux() mechanism that is currently used would work (I'm not much of an SQL guy). So a report embedded in the ticket page would have the ticket id supplied, and a report embedded in the timeline page would have the commit id supplied. #c8c8c8 303 new active 2004 Mar anonymous 2004 Mar drh 4 5 Milestone and ticket hotlists. Referencing tickets by id can be cumbersome when composing a new ticket. Typically it requires a separate browser tab to search the database. Since some tickets and milestones are referenced more than others it would make sense to make their ids and summaries available when composing a new ticket. If a new column were added to the milestones and tickets tables called hot, by checkmarking the hot column on the edit page for the ticket they could be added to a 'hotlist'. Whenever a field was presented that accepted a list of dependancies (such as the depends on field and the associated check-ins field on the edit ticket page a combo box next to the field could list all 'hotlist' ticket numbers and check-ins. When the page was submitted the entries in the combo box would be merged with the input in the text field. I think this would be particularly useful when designing with milestones, since all milestone check-ins could be marked "hot" and then when reviewing tickets I could target them for a particular release by selecting the version number from the list. Combined with suggestion #302 this would make using the timeline and milestones to plan the future direction of the project much more effective. #c8c8c8 304 new active 2004 Mar anonymous 2004 Mar drh 5 5 Option to pipe reports through an external filter. Currently reports can be displayed formatted into a table or as raw data. A third option to provide an external filter script (much like the external diff programs currently supported) to filter the report would offer several new configuration possibilities to the user. The raw data would be piped through the filter and the result returned. Two columns added to the reports table would control this. The first would contain the script command to run. The second would contain the mime type of the returned data. When embedding the result in a page the tag would be based on the mime type of the result. If it were of type text/html (or blank) it would be embedded directly in the page. If it were of type image/* it would be embeded by an image link, if it were type text/plain or ?? it would be referenced by an a anchor link. This would allow a lot of additional functionality. For instance a report that extracted ticket dependancies could be piped into a perl script that generated a dot file which in turn would be piped into dot to generate a dependancy graph. I think it would also have been possible to implement the rss feed this way. Other feeds for other systems could be generated in a similar way. Even the current report tables could be implemented as a perl script (this wouldn't make much sense however since it would then be impossible to install cvstrac as a single file). One security issue is that allowing users to configure an arbitrary filter to run on the server is not very safe :-). Such functionality would have to be limited to the server admin. #f2dcdc 305 new active 2004 Apr anonymous 2004 Apr lansil 1 1 css customization Is there scope for the site to be customized using css ? #cfe8bd 308 new active 2004 Apr anonymous 2004 Apr drh 5 3 Shaded "Initial Checkins" on Branches in the Timeline Thanks 4 that really nice tool... But it could even be better, when initial checkins on branches would be shaded like checkins on existing files in branches... That would be very helpfull... Thx in advance....John #cfe8bd 317 new active 2004 May anonymous 2004 May drh 4 3 provide simple test mechanism for email notification I have throughly tested a CVSTrac mail notification script I downloaded and customized (going so far as to run it with fake input as the webserver user. It seems to work fine, except I am receiving no CVSTrac mails, and logging does not appear to work (next bug). It may be relevant to consider actually integrating email notification into the next release, or at least packaging scripts that do mailing which are known to work under a variety of circumstances. #cacae5 324 new active 2004 May anonymous 2004 May anonymous 3 4 viewcvs/cvsweb compatibility of urls Cvstrac provides a browse capability which is (except for tickets) a strict subset of that provided by viewcvs (most common) and cvsweb (older) products. Many cvs clients assume that viewcvs or cvsweb is available and send GET-style urls to the appropriate web browser. To lessen the need to install viewcvs/cvsweb, an even larger subset of their REST architecture could be implemented. Cvstrac already does much of what cvsweb_etc does: *: directory browsing - cvstrac uses /dir?d=/path . To emulate cvsweb_etc we could use /viewcvs/path *: file download- cvstrac uses /rlog?f=/path.... cvsweb_etc emulation could be /viewcvs/path also. *: file download and versions - cvstrac uses /getfile... cvsweb_etc have either "checkout"/path?rev=.. or ~checkout~/path?rev=.. *: diff-cvstrac uses /filediff?.. cvsweb does /path.diff?r1=..., viewcvs does /path?r1=... Implementation could be simple redirects from a new function hanging off /viewcvs. /path maps to g.zExtra (as in getfile); deciding which to redirect would be based on an examination of /path and a few looks at parameters P(r1), etc. I will look into this. --Derek #e8e8bd 325 new active 2004 May anonymous 2004 May drh 3 2 Make wiki diff configurable The diff output for wiki entries should be configurable - both in terms of diff format (unified format preferred), and the ability to pipe to an external process so pretty output can be displayed. The stuff you already have implemented for the cvs external diff processes would work great for the wiki diff processes. (Note that the external diff config doesn't make clear that it only applies to the cvs part and not the wiki part.) #cacae5 329 new active 2004 May anonymous 2004 May drh 5 4 Request wiki calendar It would be really great if the wiki had a calendar. I am thinking of something where developers could show what meetings they are going to, when they will be out of the office, that sort of thing. Even nicer would be some sort of aggregation to show group calendars. This sort of thing is actually quite hard with wikis since you either end up with lots of pages (eg one per day) or some sort of horrible formatting nightmare. I love the Timeline in CVS trac so hopefully it could be part of that as well. #cacae5 332 new active 2004 Jun anonymous 2004 Jun drh 4 4 Shortcuts to favourite reports in the cvstrac page header First: what a great thing cvstrac is. Just right for what I need. Nice to look at as well. Thanks a lot for it! Here's my (minor) quibble: I have a few report types I often use and I find myself having to go to the reports page and then click the report I like there. This always feels like a little detour... ;-) If each report had a check-box 'show in favourites', those reports (with the box checked) could be displayed in an area just below the blue page header box (or in an extra line inside the box). That would allow quick access to these reports. Saves one page-load every time (the load of the 'reports' page). #f2dcdc 336 new active 2004 Aug anonymous 2004 Aug drh 1 1 Missing Fields in CVS Trac PROBLEM Not enough multi line fields SYMPTOM There is only 1 multi line field in the screen 'Create a new Ticket' SOLUTION In order to keep descriptions simple I'd like to have a set of different multi line fields: - Symptom - (Requested)Solution - Steps to Reproduce COMMENT Many people who report an issue make it 1 long story. Using separate fields for each part will force them to clearly state their point. The single line possibilities in 'User-Defined Fields' are not an option. #e8e8bd 313 doc active 2004 Apr anonymous 2004 Oct 2 2 Date shown in timeline is wrong When looking at timeline and chgview, cvstrac is off by a day, here's a sample check-in: Date: 2004-Apr-20 17:40:23 (local) 2004-Apr-20 21:40:23 (UTC) [snip] --- LDAP.pm 2004/03/22 17:02:53 1.45 +++ LDAP.pm 2004/04/21 21:40:23 1.45.2.1 Notice the 1 day difference between the date reported by chngview 2004-Apr-20 (UTC) and diff 2004/04/21, same problem shows in timeline, all dates are off by 1. I am pretty sure this is not a bug but something to do with our configuration, but can't figure out what and where to configure this. Thanks for any insight. #f2dcdc 369 doc active 2005 Jan anonymous 2005 Jan drh 1 1 Studying the source code Could anybody give me some background on the design philosophy behind cvstrac? I like the software, and I like the idea of writing native CGI applications. So, I started digging in the cvstrac sources to get inspiration. I understand individual lines, but I fail to understand the big picture. What is the guiding principle behind the subdivision in separate files. Usually, you find simple guiding principles, such as: one source file corresponds to one web page (typical in php, asp, asp.net, ...) or corresponds to one abstract data type (such as one table and its related methods, or one memory struct and its related methods, ...), or is otherwise organised around another particular guiding principle, which tremendously facilitates locating particular logic. It turns a source tree into an addressable grid, where you can almost calculate where some logic must be located, and where you can make changes, if needed. What is the guiding principle underlying cvstrac? #f2dcdc 370 new active 2005 Feb anonymous 2005 Feb drh 1 1 Why not to scan the cvs directory to get the reponsitory? Why not scan the cvs directory to get the reponsitory? I setup the reponsitory of cvstrace, but the history file don't includes all informations of the modules, so I Only can get the Reponsitories which is in history file. #e8e8bd 373 new active 2005 Feb anonymous 2005 Feb drh 2 2 Add ability to create templates for new tickets It would be helpful if we have the ability to reuse mutliple templates to open new tickets. Expected: 1: Should be able to save a template with default values set to different parameters. 2: Reuse these templates to open different types of tickets #f2dcdc 376 new active 2005 Mar anonymous 2005 Mar drh 1 1 create a .pid when run in server mode - crontab friendly I am running CVSTrac as a standalone server. It would be nice, when standalone server is launched, if it created a pid file. That way I could easily check from crontab is CVSTrac is still running and restart it if not. #cacae5 386 new active 2005 Mar anonymous 2005 Mar drh 5 4 "Show Milestones" does not show milestones generated by cvs rtag When browsing the source code of a project and clicking "Show Milestones" only milestones that were created with cvstrac show up. Milestones generated by "cvs rtag" do not. Additionally, when viewing the timeline with "Divide timeline by milestones" checked, again, only milestones entered manually into cvstrac show up in the pink boxes. It would be nice if the default behavior when "Divide timeline by milestones" is checked was to list the "cvs rtag" generated milestones without ever having to manually add a "Release" milestone in cvstrac. #cacae5 396 new active 2005 Apr cpb 2005 Apr cpb 5 4 owner should be able to lock tickets Ticket owner/assignee/admin should be able to lock a ticket against changes, similar to how wiki locking works. #cacae5 397 new active 2005 Apr cpb 2005 Apr cpb 5 4 ticket link info should contain status #392 gives title information and #52 indicates at a glance whether or not the ticket is active. However, _why_ it's not active would be extremely valuable... i.e. was it fixed or deferred? Is a ticket new or actively being worked on? If we're looking at the ticket status anyways, we might as well present it to the user... #e8e8bd 428 event active 2005 Jun anonymous 2005 Jun drh 1 2 cvstrac does not see modules, which are created via pserver I today installed cvstrac running from inetd under FreeBSD 4.11 from the port. I did setup the cvsroot path and left the module field blank, to see all modules. When browsing cvs from cvstrac I see some modules missing. When checking CVSROOT/history I saw that the missing modules were created remotely via pserver access using cervisia frontend. But I can see other remotely created modules. There are 88 modules in our repository. #cfe8bd 361 new active 2004 Dec anonymous 2005 Aug drh 4 3 localisation Hi,

I am interested in a german localisation of cvstrac. Therefore would do the translationwork!

It would be nice to see plain text sourced out to an file #cacae5 436 new active 2005 Aug cpb 2005 Aug cpb 5 4 add filters to browse directory view The ability to filter a directory view in a browse page with "globs" would be real handy when looking for something specific. All you'd need is just a textfield entry at the top of every directory "/dir?" page. #f2dcdc 448 new active 2005 Aug anonymous 2005 Aug cpb 1 1 import of svnserve users Attached diff enables _svntrac_ to import users from _svnserve_ users file. This is not equivalent to reading of CVSROOT/passwd since some installations of _Subversion_ don't use _svnserve_ and hence don't have relevant users file. This is not the best solution, but ATM I have no plans to add support for importing users from _{quote: mod_dav_svn}_ . _svntrac_ supports only import of users, and unlike _cvstrac_ , it can't update _svnserve_ users file based on the contents of _svntrac_ db. This limitation is imposed by the fact that passwords are stored encrypted in _svntrac_ db, while they are stored as plain text in _svnserve_ users file. Only way, AFAICT, to support it would be to store plain text passwords in db, but I guess this goes against _cvstrac_ design goals?{linebreak} Though it would be nice to have this "user export" feature since AFAIK there is no way to manage _svnserve_ users other then to edit users file directly. #cacae5 450 new active 2005 Aug cpb 2005 Aug cpb 4 4 append remarks could be smarter I'm starting to see where remark handling could be enhanced to have some concept of "replying" to a particular comment. Nothing as sophisticated as message threading, but maybe just filling in with the original remarks text. Something to help out in building context... This would require some way for the ticket formatter to distinguish between individual remark sections... #cacae5 243 new active 2003 Aug anonymous 2005 Aug drh 5 4 Allow more customization for the header and footer I've had a need to customize the header a bit more, keeping a company logo on the top bar, not above it. Attached to this report is a patch that allows slightly more customization. I think it would be valuable for general consumption, as I can imagine this a common need. #cfe8bd 459 doc active 2005 Aug cpb 2005 Aug cpb 5 3 Fix documentation/UI to make more sense with SVN There's a lot of references around to things like _CVSROOT/history_. #cacae5 476 new active 2005 Sep cpb 2005 Sep cpb 5 4 add support for GIT http://git.or.cz/ There's two main reasons for this. 1: Documentation. SvnTrac a poor guiding example for adding a new SCM because we were making things up as we went along. Documenting _that_ process is just going to introduce a bunch of noise. 2: Proof of concept. GIT is quite far from the CVS model. Getting it working is a good test of the whole ScmTrac concept. It appears that it shouldn't be too difficult to get things working. #f2dcdc 475 doc active 2005 Sep drh 2005 Sep drh 1 1 Add wysiwyg editing of wiki and tickets. See http://www.wikiwyg.net/ #cacae5 479 new active 2005 Sep anonymous 2005 Sep drh 4 4 Source code files should have remarks/attachments Source code should allow for remarks and attachments to be associated with a particular file. While this sort of thing could be put into the code itself, it generally is not, since it may bother the writer. And even if it were, only programmers would be able to do so. In general, there are 5 types of things in cvstrac: tickets, remarks, attachments, source code files, and wiki pages. Tickets seem to be first-class objects (#123 anywhere refers to a ticket), and Wiki pages seem to be becoming that as well. Remarks and atachments are associated only with a particular ticket or wiki page. But source code seems completely unrelated to these. Does the viewer highlight Ticket references or WikiNames in the code? It probably should not because it may make a mistake. At the same time, associating external documentation with a source file seems valuable. (One could conceive of this becoming a full-featured Literate Programming methodology). I would think that the implementation of this would be to have options on the rlog view such as: the number of attachments, number of remarks, number of tickets against a particular file, a link to the annotate/blame view (Ticket #183), #e8e8bd 484 new active 2005 Sep anonymous 2005 Sep drh 5 2 Please increase the rows and cols of the textarea in ticket page rows="20" cols="100" is preferred. Or add function let user set them by himself. Because when I write more lines, the small textarea makes me feel as look through a small window to the outsider. thanks. #cacae5 478 new active 2005 Sep cpb 2005 Sep cpb 5 4 should be able to browse tree "snapshots" Browse as currently implemented shows, basically, a union of all sets of files ever found in the repository. It would be nice if there was an option to browse the tree as a snapshot at any particular changeset. That way you don't see the deleted stuff and you don't see stuff added later. #cacae5 488 new active 2005 Sep anonymous 2005 Sep cpb 4 4 Enhancing derivedfrom (and providing backward compatibility) Currently, we used derivedfrom to record external references as to where where a ticket was derived from (e.g. change request - CRxxx etc) as well as references to other tickets (1.1.4 didn't really state otherwise) . This functionality has now changed in 1.2 . Additionally, derivedfrom can currently only reference one other ticket. I am requesting comments on the suitability of the following changes for inclusion in CVStrac (I'll do the work - however, I don't want to have to maintain my own version and will just use an 'extra' field if the following is not acceptable). *: Add additional xref table for derivedfrom tickets references. *: Preserve derivedfrom field as entered in webform for further display. *: Scan derived from field for any number or #number which hasn't been prefixed or sufixed with letters. Store these references in the new xref table. *: Use xref table to look up derived tickets for use in the ticket view #cacae5 399 new active 2005 Apr cpb 2005 Oct chorlya 5 4 add option to limit timeline size by number of lines Alternative to number of days. Also makes projects that periodically stop look more active ;) #cfe8bd 503 doc active 2005 Nov anonymous 2005 Nov drh 3 3 A Better "FormattingWikiPages" + 2 wiki bugs I have identified two outright bugs in cvstrac's wiki (probably already documented somewhere else; if not, someone on the cvstrac team should probably ticketize them and assign them to the right people): 1: If the entire link: statement will not fit on one line inside the wiki text editing box, the link command is ignored. 2: * followed by _ then some text then _ followed by * (and vice-versa) to make text both bold and italic don't work, despite everything else being nestable (e.g. *'s around a "quote:" block); the more interior of the two markups is simply interpreted as part of the "word" the exterior markup is affecting. A third issue (a misfeature) is that use of html and /html to insert arbitrary HTML code introduces a bogus, worse-than-useless linebreak, which makes the html wikicommand only usuable on large blocks of stuff, instead of inline in the middle of a sentence of whatever. That said, I was in the process of modifying my local copy of FormattingWikiPages to deal with problem no. 1 above, and just decided to overhaul the entire thing, as a way of giving back. There were several details in the editing hints at the bottom of the page when editing any wiki page, that were not in the FormattingWikiPages documents, at least one typo, inconsistent use of bold to highlight wiki markup commands, unclear phrasing in several places, and a number of other issues. So, here is my take on it, use any of it that you like. I did implement big "WARNING:" bits about bugs and other problems, that of course should come out of this version of the wikitext if you want to use it, and the issues get resolved by then. ;-) PS: If posting the wikitext into this ticket mangles it in some way, drop me a line and I'll e-mail you a copy. The preview I just did seems to indicate that cvstrack will render all the wiki commands even inside a ticket, so you can't see the wikisource. I should probably e-mail it. ***************************************************************************************** **Paragraphs** Use *one or more blank lines* to separate paragraphs. You can arbitrarily wrap text within a paragraph (or not bother to wrap it at all), _except_ that {quote:{link:}} commands cannot line wrap; see below for more details. **Indentation of Code** If the first line of a paragraph begins with a *tab* or with *two or more spaces*, then that whole paragraph is shown verbatim (that is, within 

...
markup in HTML, including the constant-width font with all spacing and line breaks preserved) The formatting rules below _do not apply_ to verbatim paragraphs (other than {quote:}, as explained next). See "Lists", below, for how to indent without 
 behavior.  **HTML**  You can insert arbitrary HTML into a wiki page, by surrounding the code to be inserted with  *{quote:""}* and *{quote:""}*.  Warning: Because text between {quote:"" and ""} is  interpreted as HTML, _even inside verbatim paragraphs_, if you need to use the string "{quote:<}html>" in sample code, you must wiki it as "{quote:{quote:}}", or your  sample code will be parsed and rendered instead of displayed as written.  This does not affect , nor other HTML or XML markup, just "{quote:}".  **Boldface and Italics**  Text contained between asterisks is rendered *bold.* If you use two or three asterisks in a row, instead of just one, the bold text is also shown at a larger point size. Text between underscores is rendered as an _italics._ All font style markers must start at the beginning of a word (a contiguous text string) and must finish at the end of a word within the same paragraph.  You cannot use both at once.  However, you can acheive the desired effect like so:{linebreak} {quote:Italicized bold text}{linebreak} but at the cost of a linebreak inserted before the text marked up this way.  **Lists**  If a line begins with the characters "*{quote:*:}*" followed by a space or tab, then that line becomes an item in a bullet list.  Similarly, if the line begins with "*N:*" (where N is any number including a multi-digit number, or 0) then the line becomes an item in an enumeration list. Enumeration items are automatically renumbered so the values of N do not need to be in ascending order.  Lines that begin with "*{quote:_:}*" are indented like a bullet list but do not display the bullet.  You can use this to indent without getting monospaced fonts and other behaviors of 
.  Make nested lists by adding colons.  For example, to make a second level bullet, begin the line with "*{quote:*::}*".  **Hyperlinks**  Links to other pages are created automatically whenever the *name of another wiki page* is mentioned in the text.  (See WikiPageNames.) If you want to put a CamelCase word in your text but you do not want it to become a hyperlink, enclose the name in "{quote: {quote: ...}}".   This auto-linking does not happen inside indented verbatim paragraphs.  Full *URLs* in the text, such as links to external sites, also automatically become links, but see below for special handling of image links.  Such auto-links are created for any URL beginning with "http:", "https:", "ftp:", or "mailto:", without having to use the {quote:{link:}} functionality documented below.   *Note:* If the URL ends with ".jpg", ".jpeg", ".gif", or ".png" then the image that the URL points to is displayed inline on the wiki page.  You can also create an inline image using markup like this: "{quote: {image: URL}}". Using the {quote: {image:...}} markup allows the image URL to be relative.  This allows an image stored in an attachment to be displayed inline.  Text of the form "*#NNN*" where the "NNN" is a valid ticket number becomes a hyperlink to the ticket.  Text of the form "*[NNN]*" where "NNN" is a valid check-in or milestone number becomes a hyperlink to that check-in or milestone.  These hyperlinks only work if the user has permission to read tickets, check-ins, and/or milestones.  To create a hyperlink on arbitrary text, use "*{quote: {link: ...}}*" markup.  Any text of the form:  "{quote: {link: URL PHRASE}}" displays PHRASE as hyperlink to URL.  Example:{linebreak} {quote: {link: http://www.google.com Google}} = {link: http://www.google.com Google}{linebreak} The URL can be an absolute URL beginning with a prefix like "http:", or it can be a relative URL referring to another page within the same CVSTrac server.  For example, to create a link to a ticket report, one might write: "{quote: {link: rptview?rn=1 Active Tickets}}".  Warning: The {quote:{link:}} mechanism cannot handle long links. If the entire {quote:{link:}} command will not fit onto one line in the wiki editing text box, the link will get mangled. If this happens, use http://tinyurl.com to create a shorter, redirect URL.  **Horizontal Lines**  A horizontal line (the 
 markup of HTML) is generated whenever four or more "-" or "=" characters appear on a line by themselves:{linebreak} *{quote: ----}*  **Other Markup Rules**  The special markup "*{quote: {linebreak}}*" will be rendered as a line break or hard return.  The content of "*{quote: {quote: ...}}*" markup is shown verbatim, including wiki commands, e.g.:{linebreak} {quote: {quote: {quote: ...}}}  ----
#cfe8bd	509	doc	active	2005 Nov	cpb	2005 Nov	cpb	3	3	need online help/user manual	There's a lot of features in CVSTrac that people don't know about at first glance because, well, there's no documentation about actually _using_ it.
#cfe8bd	513	new	active	2005 Nov	anonymous	2005 Nov	cpb	3	3	svntrac should support more than one svn repository	To be functional comparable with cvstrac, svntrac should support somthing like a parent_svn_dir and include all svn repos in this directory. At the moment we can only use one repo, which is the same like one cvs module.
#c8c8c8	532	new	active	2005 Dec	chorlya	2005 Dec	chorlya	5	5	Show text length when ticket summary too long	When one-line summary is too long it would be nice to display how long  that text is at that time. This is just to give user an idea of how far off s/he is.
#cfe8bd	265	new	active	2003 Nov	anonymous	2005 Dec	drh	2	3	Accessibility support	Can you add accessibility support to forms, please?    Just add additional atributes to buttons and input fields, example:        ...    
#cacae5	549	new	active	2006 Jan	anonymous	2006 Jan	drh	4	4	Wish:  trigger on Wiki changes (e.g. for mail)	My team would really appreciate a mail notification on wiki changes.  Also, the permission system is great; but still, every Wiki webmaster needs to take measures against illegal content and vandalism.  I understand that you would not hard-code mail in here; but could we duplicate or reuse the mechanism that is used for ticket changes?   -Karsten
#cfe8bd	557	new	active	2006 Jan	cpb	2006 Jan	cpb	5	3	create new tickets by e-mail	It'd be useful to be able to create a ticket around an e-mail message. I get a lot a bugs reported to me by mail and cutting and pasting them and any associated attachments is a pain in the butt.
#e8e8bd	563	doc	active	2006 Feb	anonymous	2006 Feb	drh	1	2	Target fix version	When creating a ticket, i would like to be able to set a string that gives the version the bug need to be fixed for (eg: 1.1)  Would be even better if this could be a drop down and that we could set some marketing version somewhere in the setup
#cacae5	572	new	active	2006 Feb	chorlya	2006 Feb	chorlya	4	4	Few usability improvments to HTML markup	It would be nice to tidy up our forms a bit. I'm thinking of adding taborder to few forms and adding =