Edgewall Software

Changes between Version 1 and Version 2 of MilestoneCustomFields


Ignore:
Timestamp:
May 6, 2009, 10:13:22 PM (15 years ago)
Author:
Josh Toft <joshtoft@…>
Comment:

More Clarification

Legend:

Unmodified
Added
Removed
Modified
  • MilestoneCustomFields

    v1 v2  
    11== Milestone Custom Fields Proposal ==
    22
    3 Here is a proposal for Custom Fields -- based on the initial concept of [http://trac.edgewall.org/wiki/SubTickets Subtickets]. See related tickets #31, #886 and #6328.
     3Here is a proposal for Custom Fields -- based on the initial concept of [http://trac.edgewall.org/wiki/SubTickets Subtickets]. See related tickets #31, #886 and #6328. The idea behind this, is in fact the opposite of the [http://trac.edgewall.org/wiki/SubTickets SubTicket] concept. We already have the ability to add custom fields to tickets, so why not make Milestones have the same options.
     4
     5=== Examples ===
     6
     7For instance, I want to have a workorder number and client attached to each milestone. And I want that visible on the roadmaps (Can do manually of course with templates). Currently, I have to make another table that matches up to each milestone, create an entire plugin for the whole damn thing, and finally connect it. Tickets have this exact functionality already, Milestones need it too.