View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005760 | mantisbt | filters | public | 2005-06-09 14:22 | 2019-12-03 10:27 |
Reporter | gtomlin | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | acknowledged | Resolution | open | ||
Product Version | 1.0.0a2 | ||||
Summary | 0005760: Reset project to user's default when [Reset Filter] selected | ||||
Description | For any user who works on more than one project (and all of ours do), it is a two step process to see all active issues. Our users therefore have "All Projects" as their default project. Whenever a user reports an issue, he/she is switched into the project under which the issue is reported. After that, [Reset Filter] only shows the issues under that project, and the user must then explicitly switch to All Projects to see all active issues. The purpose of [Reset Filter] is to remove filters and allow a user to see all issues, but as it stands at present it doesn't always do so. The results of [Reset Filter] are inconsistent because the Project is not reset. | ||||
Tags | No tags attached. | ||||
Would like developers opinions regarding this. |
|
I would classify this as a 1.3.x feature. Here is my suggestion:
If user selected the report more issues checkbox, then all issues will be reported against the previously selected project. The bottom line is not to change the context of the user due to reporting an issue. The same way we don't change the context when a user views an issue. Note that in the past, we used to switch the context when the user viewed an issue. The reset filter would continue to behave as is. Does this make sense? |
|