Mercurial > p > roundup > code
diff doc/design.txt @ 3904:91008ec8f9a0
retire "topic" usage
"Topic" still appears in the locale files. I'm sure we need to support
that for existing trackers. I *think* they don't care about any of the other
changes that have been made.
I also left Ka-Ping Yee's original design document unchanged.
This takes care of sf feature request [SF#953161]
| author | Justus Pendleton <jpend@users.sourceforge.net> |
|---|---|
| date | Sun, 16 Sep 2007 02:45:11 +0000 |
| parents | 0d561b24ceff |
| children | ba4452e91a28 |
line wrap: on
line diff
--- a/doc/design.txt Fri Sep 14 15:55:25 2007 +0000 +++ b/doc/design.txt Sun Sep 16 02:45:11 2007 +0000 @@ -819,7 +819,7 @@ Class(db, "keyword", name=hyperdb.String()) Class(db, "issue", fixer=hyperdb.Multilink("user"), - topic=hyperdb.Multilink("keyword"), + keyword=hyperdb.Multilink("keyword"), priority=hyperdb.Link("priority"), status=hyperdb.Link("status")) @@ -1250,10 +1250,10 @@ clarity):: /issue?status=unread,in-progress,resolved& - topic=security,ui& + keyword=security,ui& :group=priority,-status& :sort=-activity& - :filters=status,topic& + :filters=status,keyword& :columns=title,status,fixer @@ -1274,11 +1274,11 @@ The example specifies an index of "issue" items. Only issues with a "status" of either "unread" or "in-progres" or "resolved" are displayed, -and only issues with "topic" values including both "security" and "ui" +and only issues with "keyword" values including both "security" and "ui" are displayed. The items are grouped by priority arranged in ascending order and in descending order by status; and within groups, sorted by activity, arranged in descending order. The filter section shows -filters for the "status" and "topic" properties, and the table includes +filters for the "status" and "keyword" properties, and the table includes columns for the "title", "status", and "fixer" properties. Associated with each issue class is a default layout specifier. The