Part of lp.registry.model.milestone View In Hierarchy
The current database schema has no formal concept of milestones related to
projects. A milestone named milestone is considered to belong to
a project if the project contains at least one product with a milestone
of the same name. A project milestone is considered to be active if at
least one product milestone with the same name is active. The
dateexpected attribute of a project milestone is set to the minimum of
the dateexpected values of the product milestones.
| Method | __init__ | Undocumented |
| Method | displayname | See IMilestone. |
| Method | title | See IMilestone. |
| Method | official_bug_tags | See IHasBugs. |
| Method | userHasBugSubscriptions | See IStructuralSubscriptionTarget. |
| Method | _milestone_ids_expr | Undocumented |
| Method | _customizeSearchParams | Customize search_params for this milestone. |
Inherited from MilestoneData:
| Method | all_specifications | Undocumented |
| Method | getSpecifications | See IMilestoneData |
| Method | bugtasks | The list of non-conjoined bugtasks targeted to this milestone. |
Inherited from HasBugsBase:
| Method | searchTasks | See IHasBugs. |
| Method | getBugSummaryContextWhereClause | Return a storm clause to filter bugsummaries on this context. |
| Method | getBugTaskWeightFunction | Default weight function is the simple one. |