Differences

This shows you the differences between two versions of the page.

--- mantisbt:tagging_requirements [2007/07/31 10:27] – Added Tag Viewing section with content jreese
+++ mantisbt:tagging_requirements [2008/10/29 04:25] (current) – external edit 127.0.0.1
@@ Line 14: / Line 14: @@
 ===== 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 be a separate portion of the bug view to show all tags currently attached to a bug, as well as an input box to enter further tags to be added.  Auto-complete should be used with simple substring comparison, either against a static JavaScript list of popular tags, or using an AJAX query to the database.  The user should be able to click a tag and get a page with more information.
+ 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 tags to a report, and will be able to detach only the tags they attached. Developers will have access to edit tags and detach any tags from bugs. By default, tags will be separated by commas so that multi-word tags can be used, but it can be configured to use spaces, or any other character, instead.
 ==== Bug Viewing ====
-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.  The tag's page should also include links to various searches filtered on the tag, such as all open issues, all resolved issues, etc.
+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.  Auto-complete should be used with simple substring comparison, either against a static JavaScript list of popular tags, or using an AJAX query to the database.  The user should also be able to click any attached tag to view a page with more information.
 ==== 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.  If the user has high enough access (see threshold configuration), then they should be able to edit the tag's name and 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 'tagA -tagB' where that is interpreted as 'tagA, but not tagB'.  The system will use a case-insensitive search on existing tags, as well as looking for existing tags with or without a trailing 's' to match and use existing tags before creating new and redundant tags.
+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', 'tag', or '-tag'. In this manner, any tag noted with a '+' **must** be attached to any resulting bug, any tag noted with '-' **must not** be attached to any resulting bug, and resulting bugs must have **any** of the un-denoted tags attached, but not necessarily all of them.  The system will use a case-insensitive search on existing tags, as well as looking for existing tags with or without a trailing 's' to match and use existing tags before creating new and redundant tags.
-==== 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 ====
@@ Line 55: / Line 58: @@
     * **user_id int(10)**
     * **attach_date datetime**
@@ Line 69: / Line 74: @@
     * ''tagging_create_threshold'' (REPORTER) to create new tags when attaching to bugs
     * ''tagging_edit_threshold'' (DEVELOPER) to edit tag names and descriptions
+    * ''tagging_edit_own_threshold'' (REPORTER) to edit tags created by the same user
@@ Line 94: / Line 101: @@
 **Second Review by vboctor:**
-  * Add 'id' field to 'mantis_bug_tag_table'. (I see no need for this. mantis_project_user_list_table uses a PK of the two ids. -jreese)
+  * Add 'id' field to 'mantis_bug_tag_table'.
+    * I see no need for this. For comparison, mantis_project_user_list_table uses a PK of the two ids. (jreese)
   * Add 'user_id' field to 'mantis_tag_table'.
   * 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).