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:04] – Database and configuration changes 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 ' | ||
+ | |||
+ | |||
===== 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 once to each report. By default, anyone with reporter access will be able to create and attach |
- | When viewing tags already attached to a report, a link should be available to a page listing more information about the keyword, including the ability to enter or edit a description. | ||
+ | ==== Bug Viewing ==== | ||
+ | |||
+ | When viewing bug reports, there should be a separate portion of the bug view to show all tags currently attached, as well as an input box to enter further tags to be added. | ||
+ | ==== Tag Viewing ==== | ||
+ | |||
+ | When viewing a page for a specific tag, the user should be shown information about the tag, including a description, | ||
+ | |||
+ | |||
+ | ==== 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 ' | ||
+ | |||
+ | |||
+ | ==== 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 ==== | ||
+ | |||
+ | 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. | ||
+ | * HTML metatag keyword filling from tags. | ||
===== 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 45: | Line 74: | ||
* '' | * '' | ||
* '' | * '' | ||
+ | * '' | ||
+ | |||
Line 51: | 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 67: | 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.1185768251.txt.gz · Last modified: 2008/10/29 04:32 (external edit)