type,ticket,votes,summary,component,version,milestone,created,_changetime,_description,_reporter enhancement,886,42,Add support for Master tickets,ticket system,devel,next-major-releases,2004-11-05T12:44:10+01:00,2023-04-13T09:07:18+02:00,"It would be cool if you could create master tickets that other tickets refer to. Work could then be broken down into chunks (and assigned to different people), but the master ticket could only be closed when all referring tickets had been resolved. You could also have it so that referring tickets are excluded from the Roadmap ticket counts.",dmurphy25@… enhancement,31,30,Bug dependencies/relations feature,ticket system,devel,next-major-releases,2004-01-29T05:53:39+01:00,2022-08-30T20:23:04+02:00,"A simple list of related bugs without logical/implicit constraints might be useful. It'd be nice to be able to relate bugs and issues in a useful manner. It would also thus allow for reports showing ""a bug and all related bugs"" in some fashion, which could be neat. This would also require checking for circular dependencies/relations. ",daniel enhancement,791,11,"login/logout, authentication, and authorization",general,devel,next-major-releases,2004-09-30T06:13:49+02:00,2022-08-07T15:41:21+02:00,"I'm kind of combining a couple of things from #599 and #788 here. The main issue is that the browser caches the authentication information, so you can't log out unless you close the browser (or with Mozilla you can use certain extensions to clear the information). A related issue is that in situations where authentication is enforced to access the project, users should never be logged in anonymously. I've already gotten a patch working that will force users who logged out to log back in, allowing them to login as a different user. I'm going to try to extend this to allow users to disable anonymous access and handle these setups more appropriately.",Matthew Good enhancement,2625,10,Add option to send HTML mail messages,notification,0.11-stable,next-major-releases,2006-01-18T01:06:19+01:00,2023-09-15T04:02:49+02:00,"It would be nice if Trac was able to send notification emails in some sort of rich format, for example HTML. This way one would not have to use fixed fonts in the mail client.",tomek.piatek@… enhancement,1,7,Add a new project summary module.,general,0.6.1,topic-multiproject,2003-08-24T22:33:02+02:00,2023-03-22T06:13:07+01:00,"This module should useful information like: * Number of open tickets * Tickets targeted for each milestone * Tickets assigned to the current user (but see rather #4588 for that) * And more... ... like a project description, attachments, etc.", enhancement,217,7,XML-RPC/SOAP/etc. interface,general,0.6,unscheduled,2004-04-01T00:04:00+02:00,2019-08-11T07:31:50+02:00,It would be kinda nice to have an interface for Trac that would allow people to develop things like allowing tickets to be reported from within an application.,jon@… enhancement,2456,5,Implement API for user management,general,0.9.2,next-major-releases,2005-12-08T02:06:33+01:00,2015-05-26T20:50:57+02:00,"I'm adding this ticket to keep track of the on-going discussion about creating a new 'user detail' interface to Trac. The new interface would be something like: {{{ #!python class IUserProvider(Interface): def get_known_users(attrs=('name', 'email'), limit=None): pass def get_user_attribute(user, attr): pass def get_supported_attributes(): pass }}} Related ML thread: * http://lists.edgewall.com/archive/trac/2005-December/005771.html ",Emmanuel Blot enhancement,2464,5,Conditional fields in tickets,ticket system,0.9.2,next-major-releases,2005-12-09T11:34:48+01:00,2021-08-19T21:34:04+02:00,"Not necessarily all possible fields should be presented to the user. There could be preconditions attached to fields, for checking if they're applicable at all and for checking if the current user can actually set/modify them. Then, as an advanced case, instead of being an all or nothing situation, the possible content of one field could be dependent on the ticket state: see #1299, #2752 and [#comment:13]. === Use cases === ==== Ability to have different ticket fields for different ticket types ==== ''(original one)'' When using quite different types of tickets (bug-report, requirement, etc), there is a need for different fields depending on the ticket type. This might add just the flexibility required for complying with existing development processes. Great feature in particular when support for master and child tickets is planned, trac could be more of a requirements management system beyond the issue database approach. See also duplicates: #4028, #4643 ==== Abilty to have different ticket fields for different ticket components ==== As for ticket types, but for components. See #2752 ==== Hide the ''Keywords:'' field ==== See #3281 ==== Hide some fields for new tickets ==== See #1580. This could be achieved quite simply by putting the ticket `id` in the condition. ",johan.regnell@… enhancement,548,4,[Patch] Support for subcomponents,ticket system,devel,next-major-releases,2004-06-15T04:44:22+02:00,2015-12-19T16:59:28+01:00,"I'd like to request the addition of a subcomponent field. This would be useful for breaking large component pieces into smaller subsets. In particular, the project I'm working on includes a core engine and several plug-in style projects. It makes sense to keep it all in the same svn repository as well as the same trac db. However, with the addition of a subcomponet (or feature or something like that), the granularity of tracking for the plug-in projects would be much better.",acarter24@… enhancement,611,4,Backlinks,wiki system,0.7.1,next-major-releases,2004-07-11T14:52:44+02:00,2021-04-07T13:43:14+02:00,"A nice feature would be automatic backlink generation for wikipages. if there is intrest in this sugested enhancement i would like to contribute in coding this feature (wih a little guidance) keep up the good work!",siegfried@… enhancement,1329,4,Ticket Search should (optionally) search only non-closed tickets,ticket system,0.8.1,next-major-releases,2005-03-21T09:19:37+01:00,2015-05-26T20:50:57+02:00,"One of the popular uses for searching (I believe) is to search the ticket database if an issue has already been filed. It would help if the search would only search tickets that have not been closed. This request is similar to Ticket #584 but I would like a way to filter the results so that only open tickets are displayed in the search result. It does not help much if you need to browse loads of resolved tickets to find the one open ticket you are looking for. ''fixed typos''",Norbert Unterberg enhancement,11466,4,in-place modifying of ticket fields like in Apache Bloodhound Trac,ticket system,,undecided,2014-01-29T13:27:49+01:00,2017-06-09T09:10:48+02:00,"If one creates a [https://bh-demo2.apache.org/newticket new Bloodhound demo site ticket], it can modified afterwards by editing the ticket fields in-place! This is what's missing. The recent Trac version just has a 'modify ticket' section at the bottom of the ticket, and it's quite confusing to have it shown at the top also. Please backport the in-place editor of Bloodhound for modifying ticket fields in the top area of a Trac ticket.",s-fr@… enhancement,1233,3,Descriptions of Components,ticket system,0.8,next-dev-1.7.x,2005-02-28T15:52:00+01:00,2020-12-29T09:45:39+01:00,"One annoying problem we have with our existing bug-tracking system is that users often don't know what component to select for a ticket. They often end up choosing an inappropriate one. One could argue that better component names would minimise this, but I've often found users to be endlessly creative in their quest to misunderstand the (seemingly) obvious ;-) A nice feature of bugzilla is that the component selector label is a link to a page listing the components for the project, along with owner and description. (If you prefer the link could be a separate item, like a '?' icon.) (Currently I'm conducting a trial of trac, and I quite like it!)",Matthew Harrison enhancement,109,3,"MissingLinks, an index over missing wiki pages",wiki system,0.5.1,next-major-releases,2004-03-02T19:22:03+01:00,2018-08-04T09:54:30+02:00,"It would be good to be able to list all links that lead to non-existing pages. Also true for tickets and changesets of course. Example: http://moinmoin.wikiwikiweb.de/WantedPages",daniel enhancement,2463,3,Mandatory fields in tickets,ticket system,0.9.2,next-major-releases,2005-12-09T11:18:09+01:00,2020-08-07T00:45:49+02:00,It would be great with ability to set some ticket fields as mandatory. These fields should be verified before allowing submit when creating a new ticket.,johan.regnell@… enhancement,2662,3,assign tickets to multiple users,ticket system,0.9.3,next-major-releases,2006-01-25T13:36:02+01:00,2021-09-19T18:37:53+02:00,"It would be very nice, if I could assign a ticket to more than one user. I set the restrict owner-parameter to false and typed in two users. I tried with different syntax, but the trac system did not notice the ticket to belong to the them. Would be fine...",mala enhancement,5031,3,Queries ought to support less/great than for ordered values (i.e. priorities and severities),ticket system,0.10.2,next-major-releases,2007-03-27T10:48:40+02:00,2014-02-19T19:06:36+01:00,I.e. expand the [is|is not] operator set a bit.,macke@… enhancement,7419,3,Custom ticket status: customised ordering of statuses,ticket system,0.11-stable,next-major-releases,2008-07-09T17:52:49+02:00,2019-12-03T03:44:58+01:00,"We have a large number of custom ticket statuses now, thanks to 0.11 - it would be nice if I could define a sort order in the config file (similar to how you can do so in a [TracIni#milestone-groups-section ""[milestone-groups]""] section) so that when ordering tickets by status, they appear in my defined order.",trac+jon@… enhancement,9807,3,Wrong sections are collapsed by default!,ticket system,,next-major-releases,2010-11-10T01:38:35+01:00,2015-03-19T15:20:49+01:00,"Collapsing the sections in a ticke is great - the trouble is that the section that is used 99% of the time is the ""modify"" section which is pre-collapsed. An ideal solution would be to make this system configurable (or even user configurable). It is going to pee-off my users to now have to press that extra button... petty I know.... but its the truth.",morgand task,5478,3,Translation of Trac to Russian/Русский [ru_RU],i18n,devel,translations,2007-06-11T16:46:57+02:00,2020-02-19T03:40:39+01:00,This ticket should be used to coordinate the translation to Russian/Русский. See also TracTermsRu.,asmodai@… enhancement,6078,3,[PATCH] Enabling multiple email notification for a single user.,notification,,unscheduled,2007-09-24T15:42:43+02:00,2016-06-15T12:27:08+02:00,"Here is a simple patch to enable the possibility to provide multiple email addresses for a user. Once this patch is applyed, the user has just to write the multiple coma-separated addresses. He will receive notification on all the addresses. I've used that to provide multiple adresses (and so many people) behind components. This patch works with the latest svn, as well as with the 0.10.X branches. I also have the equivalent for the 0.9 branch if you are interested.",christophe.sauthier@… enhancement,8069,2,[PATCH] Support list of users as options list in ticket custom field,ticket system,0.11.3,next-dev-1.7.x,2009-02-18T19:57:54+01:00,2020-12-29T09:45:39+01:00,"In the process of migrating from a Borland StarTeam install to Trac+SVN, I needed the ability to assign multiple users to a ticket. Borland provided the ability to include custom Change Request fields which could be limited to the list of valid users within the StarTeam project. Attached is a patch which implements similar behavior in Trac. The patch introduces a simple variable replacement scheme to the options attribute of a custom ticket field. The INI section looks like this: {{{ [ticket-custom] devtest_assigned = select devtest_assigned.label = Dev Tester Assigned devtest_assigned.options = $userlist }}} Code in ticket/api.py checks for a select custom field which has an options attribute of literally ""$userlist"". If such a field is found, the field is passed to the existing function eventually_restrict_owner() to insert the listing of valid users. The attached trivial three-line patch appears to work well against Trac-0.11.3.",Zachary Bedell defect,1890,2,Can create tickets anonymously using the username of an authenticated user,general,0.8.4,next-major-releases,2005-08-07T23:45:51+02:00,2022-03-01T05:06:05+01:00,"I can create tickets anonymously using usernames of registered users. This is a Bad Thing(TM) in that people can impersonate me on my Trac. Or, they could otherwise pretend to be me. Which, to some users, may be confusing and misleading. It also poses a security threat in that any random person can go in and meddle in my bugs and close at will because to be able to add a comment to a ticket, you have to have TICKET_MODIFY, which essentially means anonymous has TICKET_ADMIN (filing another bug for this, since I know that at least in my projects, I like two problems to be reported as... two problems...) ---- '''Current status of the discussion''': each change to a ticket must also record whether the user who did the change was authenticated or not. See more complete summary in comment:53.",ziggy@… defect,5441,2,Timeline shows incomplete information about status changes for customized workflow,timeline,devel,next-major-releases,2007-06-07T05:39:14+02:00,2015-03-02T22:27:22+01:00,"Currently 'Timeline' shows details about status transitions only for few standard values ('new', 'reopened' and 'closed') and everything else shows as ""''status'' changed"", which is not very convenient if custom workflow has more states. We could have something like records in ticket's change history. Sample patch is attached. More generic solution (e.g. show changes in custom fields similarly) could be even better...",anonymous enhancement,2035,2,Changeset commenting,version control/changeset view,,next-major-releases,2005-09-09T15:35:21+02:00,2022-09-08T16:44:10+02:00,"Commenting on changesets would be great, it would substitute for code review tools.",polarfox@… enhancement,2344,2,sub milestone,roadmap,0.9,next-major-releases,2005-11-11T19:13:18+01:00,2021-02-19T22:18:32+01:00,"I need the feature to create children milestones. For example, I planned V1_release as a milestone. OK. Now suppose I plan alpha, alpha2, beta, beta2, rc1, rc2 release, then I'd like to associate these releases as parts of ""V1_release"". I'd like to assign these small milestones as children of greater milestone. Or another example, suppose [http://developer.gnome.org/dotplan/tasks.html gnome development process], they have some of phases for each release. Feature freeze, String freeze, Hard UI freeze, etc. If trac supports sub-milestone, then it is possible to manage these kind of release/development process. ",anonymous enhancement,2382,2,WebAdmin: resync from the web interface,version control,0.9,next-major-releases,2005-11-20T10:24:21+01:00,2015-05-26T20:50:57+02:00,"It would be nice to be able to resynchronize from the web interface. I've written a WebAdmin component that does this for any repository that supports the 'sync' method. (Should we have a WebAdmin component for tickets?)",Manuzhai enhancement,7573,2,base_url for many projects is painful,general,0.12dev,next-major-releases,2008-08-28T22:35:21+02:00,2016-09-08T15:48:46+02:00,"Setting the base_url in hundreds of ini files, and changing them with a hostname change is painful. I've attached a patch for a parent_base_url trac.ini setting that can be used in a parent trac.ini. ",doki_pen enhancement,10178,2,[PATCH] Allow TracQueries to order on multiple columns,query system,0.12dev,next-major-releases,2011-05-14T06:46:57+02:00,2021-11-10T22:37:39+01:00,"Currently trac only supports ordering on a single column. I've written a patch which provides the ability to sort on more than one column. This allows: {{{ [[TicketQuery(max=5,order=priority|somecolumn, desc=0|1, status=open)]] }}}",david@… enhancement,8417,2,CachedRepository support in TracMercurial,plugin/mercurial,0.11.1,plugin - mercurial,2009-06-25T16:09:38+02:00,2022-06-09T23:59:56+02:00,"I used trac with svn, and switched to mercurial. the revision table in postgres is no more updated with new changesets. So when I do a search in changesets, new changesets are not listed. Did I forgot to configure something?",asterix@… enhancement,1505,2,Search all projects at once,search system,0.8.1,topic-multiproject,2005-05-03T13:22:01+02:00,2015-05-26T20:59:54+02:00,"In case of mulitple projects, it would be very interesting to have a global search (across all projects and their tickets). Is suppose this would be quite easy to accomplish, if this would call the search of each separate project and display the results in a single page ...",anonymous enhancement,508,2,'Related checkins' feature,ticket system,0.7,unscheduled,2004-06-03T20:52:37+02:00,2010-11-17T09:24:44+01:00,"In CVSTrac, a ticket has a field called ""Related Checkins"" which shows a list of checkins (they would be changsets in trac) and their comments. You can add and remove from this list by editing a comma-seperated list of related checkins. However, the most useful part, is that by putting a ticket number into your checkin message, it automatically adds that checkin to the ""Related Checkins"" of the ticket. Eg. svn commit -m 'Added the ability to edit existing tickets. This fixes ticket #411' Then when you view the ticket #411 you can see that checkin there without doing any more work. This feature made CVSTrac sooo useful, because it was very easy to make this connection from the ticket to the checkins that attempted to fix it. bonus marks: The whole idea of two-way linking useful in general -- once you had this feature you might also show wiki pages linking to a ticket, or tickets linking to a wiki page. Often with information given by people, the incoming links are as relevant as the outgoing ones. BUT the automatic pingback from the checkins to the tickets is by far the most useful! ",dobes enhancement,4781,2,Scheduled report by mail to specific users,report system,,unscheduled,2007-02-19T13:24:08+01:00,2015-07-28T10:31:07+02:00,"It would be good to have possibility to schedule a report for example as a job of the Windows or Linux server, which will be sent to specific list of people - for example Project Manager will be informed weekly about numbers of defects.",dmusil@…