mantisbt:tagging_requirements
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
mantisbt:tagging_requirements [2007/07/30 00:31] – jreese | mantisbt:tagging_requirements [2008/10/29 04:25] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 8: | Line 8: | ||
Because of the ' | Because of the ' | ||
+ | |||
Line 13: | Line 14: | ||
===== Proposed Approach ===== | ===== Proposed Approach ===== | ||
- | All tags will be stored in a database table, with a separate table containing foreign key links between bugs and tags. There should | + | All tags will be stored in a database table, with a separate table containing foreign key links between bugs and tags. A tag may only be attached |
==== Bug Viewing ==== | ==== Bug Viewing ==== | ||
- | When viewing tags already | + | When viewing |
+ | ==== Tag Viewing ==== | ||
+ | |||
+ | When viewing a page for a specific tag, the user should be shown information about the tag, including a description, the user who created it, when it was created and last updated, how many bugs it has been attached to, and five tags that were attached the most to the same bugs. | ||
==== Filters ==== | ==== Filters ==== | ||
- | When using the filters page in normal mode, a simple multi-select box containing a list of tags will be used to choose what tags to filter on. In advanced mode, a free text input will be used, where the user can list out tags to filter on, in the form 'tagA -tagB' | + | When using the filters page in normal mode, a simple multi-select box containing a list of tags will be used to choose what tags to filter on. In advanced mode, a free text input will be used, where the user can list out tags to filter on, in the form '+tag', ' |
+ | |||
+ | |||
+ | ==== Management Decisions ==== | ||
+ | |||
+ | * If a tag has been removed from all reports that it has been attached to, it should not be removed from the database for history and data reasons; it should be manually removed by someone with appropriate access. | ||
+ | * When renaming or deleting tags, associated bugs should have their histories appropriately updated with an event noting the change: noting that the tag has changed names (renaming) or has been removed (deleted). | ||
==== Future Possibilities ==== | ==== Future Possibilities ==== | ||
The initial implementation will not provide these features, but they could be included in future updates: | The initial implementation will not provide these features, but they could be included in future updates: | ||
+ | * Using tag clouds for reporting and other views. | ||
* Auto-tagging reports based on unique actions or events, such as source control submission, etc. | * Auto-tagging reports based on unique actions or events, such as source control submission, etc. | ||
* HTML metatag keyword filling from tags. | * HTML metatag keyword filling from tags. | ||
Line 32: | Line 45: | ||
===== Database Changes ===== | ===== Database Changes ===== | ||
- | * Create '' | + | * Create '' |
- | * **id int(10)** with // | + | * **id int(10)** |
- | * **name varchar(100)** | + | * **user_id int(10)** |
+ | * **name varchar(100)** | ||
* **description text** | * **description text** | ||
* **date_created datetime** | * **date_created datetime** | ||
* **date_updated datetime** | * **date_updated datetime** | ||
- | * Create '' | + | * Create '' |
- | * **bug_id | + | * **bug_id |
- | * **tag_id | + | * **tag_id |
+ | * **user_id | ||
* **attach_date datetime** | * **attach_date datetime** | ||
- | * **attach_user int(10)** | + | |
+ | |||
Line 57: | Line 74: | ||
* '' | * '' | ||
* '' | * '' | ||
+ | * '' | ||
+ | |||
Line 63: | Line 82: | ||
Any feedback should be placed below. | Any feedback should be placed below. | ||
+ | **First Review by vboctor:** | ||
* By default table names start with mantis_ prefix (vboctor) | * By default table names start with mantis_ prefix (vboctor) | ||
* Consider capturing the tag creation date and last update date in the tag definition table. (vboctor) | * Consider capturing the tag creation date and last update date in the tag definition table. (vboctor) | ||
Line 79: | Line 99: | ||
* What will happen when a user is deleted? | * What will happen when a user is deleted? | ||
* We should add group actions to add/remove tags. (vboctor) | * We should add group actions to add/remove tags. (vboctor) | ||
+ | |||
+ | **Second Review by vboctor:** | ||
+ | * Add ' | ||
+ | * I see no need for this. For comparison, mantis_project_user_list_table uses a PK of the two ids. (jreese) | ||
+ | * Add ' | ||
+ | * Define the indices. | ||
+ | * We talked about a tag cloud (put it in future possibilities if you are not planning to include it in initial implementation). |
mantisbt/tagging_requirements.1185769861.txt.gz · Last modified: 2008/10/29 04:31 (external edit)