369371 - Abillity to query in footer by a imported bug source installation id.

Status: NEW

(Bugzilla :: Bug Import/Export & Moving, enhancement)

Description

[Guzmán Brasó]

Hi!

I did many years ago this for the company I work for.

In summary this it what I have:
1. Add to Moving bugs configuration "enable-source-id-search"
2. Add to Moving bugs configuration "source-id-search-urlbase"
3. Add to footer that if enabled add a field like "find id" but "find remote id", action of this is show_bug_byremoteid.cgi.
4. show_bug_byremoteid.cgi it's a show_bug.cgi which at starts takes $id value, search database to look for the local id of the bug that came from "source-id-search-urlbase" urlbase. Then change $id for the local id and let code continue.

I force to give me urlbase because I usually have other urlbases submitting bugs for testing and I know developers will not want to find a bug moved other than production installation.

I know show_bug_byremoteid.cgi is useless and it should be added into show_bug.cgi the functionality, I did it the other way because it was easier to keep working among bugzilla versions, just copy show_bug.cgi and change a couple of lines :-). If enhancement accepted I can submit a patch adding the functionality in show_bug.cgi, the rest I think it's how it should go for Bugzilla too.

This very small change was extremely welcome by developers and product managers.

Now the question is:
Do Bugzilla want to add such feature? I'll be glad to contribue it.
I know the more efficient way will be to put in show_bug.cgi, but that will mean this feature will have to wait for 3.2 right?. And that will means lot of time right?

Then maybe I can proovide a script that patchs this in contrib so it can be released in 3.0 and add it to bugzilla code in 3.2. 

Any comments?

Comment 1

[Frédéric Buclin]

We won't take it for 3.0. Then we will need a more global discussion at a Bugzilla meeting to decide how to interact with other installations.

Comment 2

[Guzmán Brasó]

Ok, I'm totally agree on discussing this on the meeting. 

Any way this has nothing to do with bug 369275 nor WebService. 

This enhancement is a local feature and do not interact with other installations.

Comment 3

[Max Kanat-Alexander]

You could write it as a plugin, but as you described the implementation, we wouldn't take it. We won't add a new box to the footer just for moved bugs.

What you should do is add a column to the bugs table as I said in bug 369275, and then people can search on that field using the boolean charts if they want.

Comment 4

[Guzmán Brasó]

OK. The best will be to see how bug 369275 ends taking this information, then user will be able to search with boolean for it. 

But searching through buglist means one click, one page that load, put your bug id, one click/enter, one page that load, click over the bug, load a page with your bug. In summary you were requried to do three clicks, three page loads and to insert the source id to get a bug given a source installation id. In my propposal you just put your inserted id, one click, one page load. You save 2/3 of the time you would spend to do it through buglist.cgi.

I guess my propposal would be only useful for installations that 90% of their submitted bugs are imported ones. 

May I ask why we would not take a new feature in footer.html if the admin have the option to enable it/ disable it and even we can give the option to show it ONLY to movers users, the ones that such feature would make their life a lot easier as they need a lot of time per day to check a bug given the bug source installation id? Users who don't see this useful, would not even know it exist.

Truly for me this wasn't that useful, I made it just to make my life easier while testing bugs move. But one day one of the movers of the production version saw it in testing version and asked me to put it on the production version, Since then it's heavy used and all movers asked me why the hell I didn't told them I had this feature before.

Comment 5

[Teemu Mannermaa (:wicked)]

While I don't really understand what this bug talks about, how about adding this to quicksearch? That way it's always available from the footer.