Justin Mason wrote: >> * Needinfo bugs >> >> Yeah, this concept doesn't exist in our bugzilla yet. However, the >> problem of identifying old, rotting and probably obsolete bugs that need >> additional information by the reporter has been brought up on the users >> list. >> >> Since a NEEDINFO Status (as featured by GNOME bugzilla) is a custom >> hack, we can't get that. Bummer. A "needinfo" keyword could easily do >> the same, though. This would help in searches and identifying stale bugs >> in the future. > > Here's where I'd be curious what Mark's opinion is, since he's the > maintainer of our BZ installation...
Bugzilla 3.2 includes the ability to customise the workflow. However, in the mean time I can port the NEEDINFO implementation from the main Bugzilla instance. It actually makes my life easier since it brings the main instance and the SA instance closer together. I'll need to check what the implications are on your security flag stuff since that is a custom hack too and if I recall some of the changes are in similar areas. If you want to go ahead with this, create a JIRA ticket and I'll make the changes. >> Oh, and please do not use Resolution LATER and REMIND. :) They are >> deprecated and considered harmful upstream. Actually, they are just a >> mind boggling logic flaw in the first place -- neither is a resolution. >> >> Do we have direct access to the database? In that case I'd propose to >> get id of them in the UI, which at least prevents them from being used >> any further. > > Mark -- thoughts? It should be possible to remove these although I don't know how painful it would be. If it is simple, I am happy to do it on request. If it turns out to be too painful then you might have to wait until 3.2 is released (should be soon). Again, open a (separate) JIRA ticket for this change if you decide you'd like it. Mark
