Changes between Version 132 and Version 133 of ProjectManagementIdeas

Timestamp:

Oct 20, 2015, 7:50:41 PM (9 years ago)

Author:

figaro

Comment:

Added link to Trac case studies

ProjectManagementIdeas

@@ -253 +253 @@
 == Resource Description and Allocation
 
-We need a proposal for how to describe available resources within Trac. If tasks are tickets and tickets have owners who work on them, it seems reasonable that a resource is a Trac user. There may be information we need to track for a resource that it not part of the user configuration. It might also be necessary or desirable to allow tickets to have multiple owners. Or, we might want to have a way to have a list of `(resource,hours)` pairs independent of the owner.
+We need a proposal for how to describe available resources within Trac. If tasks are tickets and tickets have owners who work on them, it seems reasonable that a resource is a Trac user. There may be information we need to track for a resource that is not part of the user configuration. It might also be necessary or desirable to allow tickets to have multiple owners. Or, we might want to have a way to have a list of `(resource,hours)` pairs independent of the owner.
 
 == Trac Core
 
-There are a couple of tickets ([t:#31], [t:#886]) and some discussion about ticket [http://trac.edgewall.org/wiki/TracDev/Proposals/TicketLinks linking] and [http://trac.edgewall.org/wiki/TracDev/Proposals/TracRelations relationships] in the Trac core.
+There are a couple of tickets ([t:#31], [t:#886]) and some discussion about ticket [http://trac.edgewall.org/wiki/TracDev/Proposals/TicketLinks linking] and [http://trac.edgewall.org/wiki/TracDev/Proposals/TracRelations relationships] in the Trac core. There are also some [t:TracCaseStudies] with uses of Trac in a project management environment.
 
 == Trac Plugins