Changes between Version 30 and Version 31 of TracFeatures
- Timestamp:
- Feb 27, 2015, 3:50:52 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracFeatures
v30 v31 2 2 '' '''Note:''' This page doesn't belong to the "official" Trac documentation and consists entirely of user contributed comments.'' 3 3 4 = What is Trac? =4 = Trac Main Features 5 5 6 6 Exactly what is Trac? What does it do? Do I need Trac? Why is Trac the best /insert class here/ in the field? 7 7 8 = Trac Main Features =8 == Open source project management tool 9 9 10 == Open source project management tool ==11 10 Trac is a lightweight project management tool that is implemented as a web-based application, written in the Python programming language. It emphasizes ease of use and low ceremony, and is [http://en.wikipedia.org/wiki/Open_source_software open source]. 12 11 13 12 Ideal for managing software developments, it is flexible enough to use for many types of projects. As it's open source, if it doesn't quite fit your needs, you can always make changes yourself, write plugins, or commission someone else to do so. 14 13 15 == Ticket system == 14 == Ticket system 15 16 16 ''Trac''k the progress of resolving individual bugs, issues, feature requests, and ideas - each with its own [TracTickets ticket] (numbered, as in a waiting room queue system). Easily reconcile overlapping tickets (where more than one person reports the same thing). Search and filter tickets by severity, project component, version or owner (among others). 17 17 18 == View progress == 18 == View progress 19 19 20 Trac gives you a number of convenient ways to stay on top of events and changes within a project. You can set milestones, and view a [TracRoadmap roadmap] of progress towards them (as well as historical achievements) in summary. There is a [TracTimeline timeline] of individual changes so you can see the order of events, starting with the most recent. [TracRss Trac supports RSS] for content syndication: allowing people to subscribe to those changes outside Trac itself, as well as [TracNotification email notification]. 20 21 21 == Online repository viewing == 22 == Online repository viewing 23 22 24 Trac gives a highly usable browsing and management front-end for [http://subversion.tigris.org/ Subversion], a modern open-source [http://en.wikipedia.org/wiki/Version_control version control system]. Trac gives you clear and elegant code highlighting and file comparison, so you can easily see how files differ. Using plugins, Trac also supports other version control software. 23 25 24 == User management == 26 == User management 27 25 28 Trac has a simple [TracPermissions permission system] to control what users can and can't access. Can be enhanced with th:AccountManagerPlugin and other plugins. 26 29 27 == Wiki == 30 == Wiki 31 28 32 [TracWiki Built-in documentation server], which can be used for developer or user resources. As it's a [http://en.wikipedia.org/wiki/Wiki Wiki], it can be set up to allow shared editing. Uses MoinMoin syntax and magic links to tickets, reports and source. 29 33 30 34 Wiki pages can start from a [wiki:PageTemplates template]. 31 35 32 == Features provided through plugins == 36 == Features provided through plugins 37 33 38 There are a [PluginList range of plugins available] supporting additional features, from anti-spam to Gantt charts and [TimeTracking time tracking]. See also [http://trac-hacks.org Trac-Hacks] for several plugins and hacks. 34 39 35 == Discussion ==40 == Discussion 36 41 37 === Things I don't know Trac has or hasn't: (questions) === 42 '''Note''': these are user contributed entries. 38 43 39 * '''Q''': Bug categories? (there's priorities, severities and keywords you can abuse for this) (Or maybe we can use [http://trac.edgewall.org/demo-0.12/wiki/TracTicketsCustomFields custom fields] for this? ) 40 * '''A''': Yes, you can categorize in many ways. Start on TracTicketsCustomFields. 41 * '''Q''': Development Calendar? (think so; at least I see one in our test installation) 42 * '''Q''': Bug type flow (e.g. bugs migrate from unconfirmed->prioritized->confirmed->fixed)? 43 * '''A''': This can be found in trac.ini, see TracWorkflow 44 * '''Q''': Is there a "resource planning" possibility? Something that Gantt charts would provide, maybe? 44 === Things I don't know whether Trac has or not 45 46 * '''Q''': Bug categories? 47 * '''A''': Yes, you can categorize in many ways. Start on TracTicketsCustomFields. There are priorities, severities and keywords you can abuse for this. Or maybe you can use [http://trac.edgewall.org/demo-0.12/wiki/TracTicketsCustomFields custom fields] for this? 48 * '''Q''': Development Calendar? 49 * '''A''': Think so; at least I see one in our test installation. 50 * '''Q''': Bug type flow, eg bugs migrate from unconfirmed -> prioritized -> confirmed -> fixed? 51 * '''A''': This can be found in trac.ini, see TracWorkflow. 52 * '''Q''': Is there a "resource planning" possibility? Something that Gantt charts would provide? 45 53 * '''A''': There's a Gantt chart plugin at PluginList, check there. 46 54 47 ==== Comparisons ==== 48 To make this page particularly valuable, consider which features Trac sports/lacks in contrast to other popular systems, such as BugZilla, JIRA, Confluence, MediaWiki, FogBugz. 49 - Wikipedia hosts a [http://en.wikipedia.org/wiki/Comparison_of_issue_tracking_systems comparison of issue (& bug) tracking systems] ...although Trac's entry is a bit out of date. 55 === Comparisons 50 56 51 If this page covers both its relative strengths and weaknesses, this would be a great page -- letting potential users know exactly what they'll get, how much work they'll need to do to get it running, and what competing packages can offer! 57 To make this page particularly valuable, consider which features Trac sports/lacks in contrast to other popular systems, such as [https://www.bugzilla.org/ BugZilla], JIRA, Confluence, MediaWiki, FogBugz. 58 Wikipedia hosts a [http://en.wikipedia.org/wiki/Comparison_of_issue_tracking_systems comparison of issue (& bug) tracking systems], although Trac's entry is out of date. 52 59 53 === Rationale === 54 ... and why not discuss all of this on the MailingList? ;) 60 If this page covers both its relative strengths and weaknesses, this would be a great page: letting potential users know what they'll get, how much work they'll need to do to get it running, and what competing packages can offer. 55 61 56 . . . I was trying to create a page that answers the first [TracFaq FAQ]: [TracFaq#Whereisthefeaturesummary Where is the features summary]. 62 === Rationale 63 64 This is a page that answers the first [TracFaq FAQ]: [TracFaq#Whereisthefeaturesummary Where is the features summary]. 57 65 58 66 * This page would be a '''great''' help for people needing to pick an issue tracking system out of the myriad available. 67 * Well, I read this, and it did not help me with my question at all: "Could Trac be useful for me and my Projects?" 68 - so true, this page eventually needs a ''total conversion''. 69 * I just want to know when one trac can connect to more than one svn repository. thanks! 59 70 60 * Well, I read this, and it did not help me with my question at all: "Could Trac be useful for me and my Projects?" 61 - so true, this page eventually needs a ''total conversion'' ;-) 62 63 * I just want to know when one trac can connect to more than one svn repository. thanks! 71 These points are best dicussed on the MailingList.
