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/31 10:23] – jreese | mantisbt:tagging_requirements [2008/10/29 04:25] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 14: | 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 once to each report. By default, anyone with reporter access will be able to create and attach |
==== 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 ==== | ||
+ | ==== 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 ==== | ||
Line 51: | Line 58: | ||
* **user_id int(10)** | * **user_id int(10)** | ||
* **attach_date datetime** | * **attach_date datetime** | ||
+ | |||
+ | |||
Line 65: | Line 74: | ||
* '' | * '' | ||
* '' | * '' | ||
+ | * '' | ||
+ | |||
Line 90: | Line 101: | ||
**Second Review by vboctor:** | **Second Review by vboctor:** | ||
- | * Add ' | + | * Add ' |
+ | * I see no need for this. For comparison, | ||
* Add ' | * Add ' | ||
* Define the indices. | * 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). | * 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.1185891826.txt.gz · Last modified: 2008/10/29 04:31 (external edit)