View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003803 | mantisbt | filters | public | 2004-05-01 08:54 | 2017-01-31 04:02 |
Reporter | vboctor | Assigned To | cproensa | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Target Version | 2.1.0 | Fixed in Version | 2.1.0 | ||
Summary | 0003803: Provide a way to update a saved filter | ||||
Description | Currently to update a filter the user has to do the following:
There should be an easi way to do this. A possible scenario is:
| ||||
Tags | No tags attached. | ||||
Agreed... was going to submit something like this. Changing a filter is difficult to do because you have to delete it and create it again. No way to edit an existing one right now. |
|
Related issue: Rename filters. Currently, you have to
|
|
Dirty soultion to update filter is to comment-out check: --- query_store.php-orig Fri Nov 12 17:00:13 2004
|
|
This is related to 0006551 (edit + rename filters) |
|
This feature would be very nice - because its an old feature wish, is it planned in one of the next releases? |
|
I am assuming that Narcissus is not working on it anymore, hence, unassign to make it available to other developers. |
|
I had a look at this issue, here is what I think we need to do:
|
|
@vboctor: "Investigate what does -1 mean, if it is "all projects", then it doesn't make sense." If I'm right, a negative number is a project specific filter, "0" a filter, which is available in "all projects". For that result I analysed filters of my private installation - hope someone could commit my result |
|
We have this implemented locally. I'll work on merging it in. |
|
Hi Daryn I take it from the long silence on this issue, that you must be busy with other things ;-) I on the other hand have a bit of time on my hands, and since this feature has been requested by my users, I would not mind implementing it. If that's OK for you, please upload what you've got (or send me by mail) and I'll start working on a patch. Or let me know if I should rather use as a basis the code written by mkornatzki in 0009213. |
|
Damien, I have a published branch for this at github which I believe is near complete. I simply haven't had time to finish testing and bug fixes. I have merged with latest master and cherry picked a few bug fixes from my custom installation. Hopefully I haven't introduced more bugs but it is certainly possible as this was a very quick merge. This branch covers stored queries as well as modifications for my view and the stored query select menu on the bug filter. It may need a migration function to get existing stored filters into the new format and probably needs the language files updated as there were a few changes I made to the english file. Any help is appreciated. Here is the link https://github.com/daryn/mantisbt/tree/save-filter |
|
Also, I believe the branch actually fixes several other filter bugs. It allows users to specify an access level required for public filters...probably a few other things as well but it's been a while. Let me know if you have any questions. |
|
Thanks for the update Daryn. I must admit, was kind of hoping to have a fix for this in 1.2.x, but by the looks of the first few commits in your github branch, I think that might be a bit difficult to achieve with this code base... Oh well, users will just have to wait for 1.3 then ;-) Nevertheless, I'll have a closer look at it. Do you have any other kind of notes, doc, test script, etc. that I can use ? |
|
Since this is a new feature it will not be allowed in 1.2. It could potentially be backported in a branch if someone really needed it. Unfortunately, what I have on github is all i've got for now but you may certainly ask if you have any specific questions. I'm frequently in the #mantishelp channel on irc if you need a quick response. |
|
Unassigned after having been assigned for a long time without progress. |
|