View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010082 | mantisbt | tagging | public | 2009-01-24 22:52 | 2015-08-18 11:13 |
| Reporter | miranda | Assigned To | jreese | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.2.0a3 | ||||
| Target Version | 1.2.0rc1 | Fixed in Version | 1.2.0rc1 | ||
| Summary | 0010082: Deleting a tag does after filtering by that tag results in error 2200 | ||||
| Description | Wanting to delete a tag in its entirety (not just the references) and lacking a tag management page, I proceeded to filter by tag on status:any issues. Having deleted the tag in the first matched issue, a refresh on my original view_all_bug_page.php resulted in an error: Application Error 0002200 - Cannot find tag by that name This looked to be caused by the existing filter which was set to filter by tag 'foo', which no longer existed, ultimately confirming the error. This has been somewhat corroborated by nuclear_eclipse, after reporting and discussing it on IRC. A logout -> empty cache -> restart browser sequence is sufficient to alleviate the symptoms. As far as resolution is concerned and with my limited knowledge of the codebase, there may be 2 or more possible solutions: 1 - Reset entire current filter in its entirety after tag deletion logic I would suggest (3) given the user knows they just deleted the tag, so 'no matches' is also an expected output, confirming the operation. | ||||
| Steps To Reproduce |
| ||||
| Tags | No tags attached. | ||||
|
I think probably the simplest way to resolve this is by modifying the tag API to either:
However, this doesn't solve the root cause of the problem, in that deleting a tag does not currently modify existing filters to remove references to that tag. I suspect this is probably true of just about all of our API's, but I could be wrong. Will investigate, and commit a solution as time permits. |
|
|
Fix committed to 1.2.x development tree. |
|