This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
At the URL above there are a few useful URLs - query issue DB, enter new issue, etc. However none of them are project-specific - if I click "enter new defect", I wind up on the huge "choose component" page. Logically, since I'm already on the junit project site, I probably want to file a new defect against the junit project. It would be nice if the links on the page recognised that, and the servlet could use some project-specific parameters so that junit is automatically chosen where appropriate (eg "&component=junit").
This is defnitely a limitation of the single IZ database that is implemeneted for NetBeans. We will take this request to our internal team for review.
You can still have a single IZ database for NetBeans; all that needs is to change the ProjectIssues servlet (I'm using the Defect link as an example) from generating this link: http://junit.netbeans.org/issues/enter_bug.cgi to this link: http://junit.netbeans.org/issues/enter_bug.cgi?component=junit ^^^^^ ^^^^^ The servlet should already know the component parameter, since it used it to generate the project URL. It should literally be a one-line change to the servlet source; since it is project-independent, this change should work on all any CollabNet project that uses this servlet, not just for NetBeans.
Here is the current workaround that you can use for now; since I doubt if any IZ enhancements will be accepted. ================================= You can use the bookmark option in Issue tracker to achieve this. - Enter the required values in the 'Enter issue' page - Click on the <Remember values as bookmarkable template> button - Click on the <to this link> link - Book mark this link using the bookmark option in the browser (the button is under the Description bar) When the book marked page is visited using this browser, the values entered are retained. ===================== The workaround allows users to store these templates for multiple components. Since most users work on a few components, this workaround will suffice. Maybe some of the users are already using this workaround. Jack, let us know if this will work.
Are you sure that the ProjectIssues servlet is part of IssueZilla? My understanding is that IssueZilla is a collection of CGI scripts, not Java servlets. I agree that CollabNet is not likely to change IssueZilla since they didn't write it, but I'm sure they wrote the project access servlet to it. The real workaround for my project is simple: don't use the shared servlet and instead just write my own static page. What I'm trying to do is fix this at a more global level to improve our whole team's pages, because that is what senior staff engineers are supposed to do.
Yes, ProjectIssues servlet is part of Issuezilla (while it wasn't part of Bugzilla). That's how the integretion is accomplished within CEE. That being said it would be possible for you to change the ProjectIssues template (I think...need to confirm) to haqrd-code this component value.
I think it would be possible to make the specific changes via remote branding AND overrides for the ProjectIssues servlet template. I am assuming that you would want this as a default behavior across the site. I will summarize the requirement. Current behavior: ProjectIssues servlet takes you to: http://<proj_name>.netbeans.org/issues/enter_bug.cgi Requested behavior: ProjectIssues servlet should take you, by default, to: http://<proj_name>.netbeans.org/issues/enter_bug.cgi?component=<proj_name> If someone is not planning to file a ticket against that component, then they can choose to see a full list. Let me know if this is OK with you.
Updating SWB.
Yes, that looks perfect. It's a small change, but any small obstacle we can remove from someone filing a bug improves our chances of actually getting their feedback. Thanks for your help.
If this is possible via branding, pls point me in the right direction :-) Thanks.
As I mentioned earlier, part of it is doable, as mentioned in /scdocs/RemoteBranding. However, this also requires some overrides that can be done by CollabNet Branding engineer. Once those overrides are in place, some modifications, changes are possible via the remote branding.
Updating the internal request tracking this.
changing the status..
to crm
Jack, We are planning to provide a separate link below the "Issue Tracking" link in the project tools navigation bar. This link when clicked would take the user to the enter_bug.cgi page for that specific project (eg "&component=junit". We would be applying this branding on the stage site that we currently have for the upgrade so that you can test it and provide your feedback. I'll update you once this branding has been applied on the stage box. Regards, Karishma Support Operations
Jack, We have changed the link 'Issue Tracking' in junit.stage.netbeans.org to point to http://junit.stage.netbeans.org/issues/enter_bug.cgi?component=junit. Now, when the user clicks on 'Issue Tracking' from this project, he would be taken to the enter issue page for the component 'junit'. If we wants to file an issue for some other component, the user can click on 'New' from the enter issue page which takes the user to the choose component page. We have done this change in the left-nav.js file on the junit.stage.netbeans.org. We were not able to pass the argument for all projects, as the left nav for each project has been customized using a javascript which overrides our navigation file. To make this change for other projects, the project owners would need to manually change the Issue Tracking link in the left-nav.js file in their project to something like: http://projectname.netbeans.org/issues/enter_bug.cgi?component=projectname Please test the link for junit.stage.netbeans.org and let us know if we can make the change on the production site as well. Regards, Karishma Support Operations
I don't understand: how is it that all of the other left-nav.js links (with URLs such as /servlets/ProjectEdit) can have project-specific parameters without editing the file, but /servlets/ProjectIssues cannot? If you can't change the text of /servlets/ProjectIssues directly, it should be easy to create something like /servlets/ProjectIssues2 which builds and invokes the project-specific link you describe, then modify the left-nav.js template. We'd handle this request ourselves except that CollabNet controls access to those servlets -- it should be a trivial change. Is the issue that servlets don't support redirection? I would be very surprised if that were true.
As Tom says, we're not asking for left-nav.js to be updated. That's our JavaScript hack to allow module sites to have some kind of dynamic navigation. I don't expect Collab to touch those files. Pls re-read the original request. We are talking about the links on http://junit.netbeans.org/servlets/ProjectIssues. Ani suggested in April 2006 that this might be possible via a combination of branding and changes on Collab's end.
Jack, An alternate would be to create a redirect rule via instance set such that /servlets/ProjectIssues redirects to issues/enter_bug.cgi?component=<projectname>. Please let us know if this option would help. Regards, Karishma Support Operations
Jack, We are awaiting your confirmation to include the changes in the instance set. Please let us know thoughts on the change suggested above. Regards, Karishma Support Operations
!? /servlets/ProjectIssues shows a find form, a query link, 5x types of enter defect links, and some other useful stuff. Having that page instead redirect to a single one of those links is ... about 5 steps backwards for 1 step forward. No, I do not think that is a good idea.
Jack This would have been doable if the branding files provided by us were not overridden by a lot of custom versions & it is unfriendly for people who are unaware of these customizations to understand which of the files in the look project repository are valid files, and what exactly they do. In many cases, like this one, it is made impossible for us to customize the templates in a way which would be convenient for you for which we handled the left-nav.js. Regards, Ramya Support Operations
Heh, sorry to hear you find our overrides unfriendly :-) Friendly or not, easy or difficult, we need to move forward. It is true, we have a lot of complex overrides to get the site looking as it does. However they affect only header, left/right nav, and footer. The links we are talking about are in the content area of the page. AFAIK that area of that page is vanilla CEE. Eg we do not use any Snippets etc. So I don't think our overrides really affect this issue, though I could be wrong. The possibilities I see are : 1) Edit the servlet. Add &component=$project to each URL in the bulleted list, as suggested here 20 months ago. Seems like the obvious fix, seems like it would apply everywhere, and benefit every project, on all CEE sites. 2) We can do it ourselves, via some overrides and branding. Ani suggested that would be possible 15 months ago, but we're still waiting on info about how to do it. The doc he mentioned is a generic overrides doc and I don't know what he exactly was thinking. Your last comment also suggests that would be possible, but other than it being difficult you don't give any details, so I'm just guessing. So, how do you propose we move towards a solution ? Thanks.
>>1) Edit the servlet. Add &component=$project to each URL in the bulleted list, as suggested here 20 months ago. Seems like the obvious fix, seems like it would apply everywhere, and benefit every project, on all CEE sites. I am checking once again with my internal team on the above said changes. >>2) We can do it ourselves, via some overrides and branding. Ani suggested that would be possible 15 months ago, but we're still waiting on info about how to do it. The doc he mentioned is a generic overrides doc and I don't know what he exactly was thinking. Your last comment also suggests that would be possible, but other than it being difficult you don't give any details, so I'm just guessing. As Ani suggested it would have been possible only if the overrides were absent through Remote Branding files. Regards, Ramya Support Operations.
I recommend we close this issue, as it should be much more easily resolved (if it's even an issue) by the BBC team next year.
When IZ of each project is clicked ,it should navigate to the IZ of the corresponding project like http://junit.netbeans.org/issues/enter_bug.cgi?component=junit&issue_type=DEFECT, instead of http://junit.netbeans.org/servlets/ProjectIssues In order to accomplish this,when we assume the component is always the project name, we can set a apache redirect rule for redirecting all requests as said above. However this involves change in inst set.Need your approval if you would like to proceed with the request because it has to be forwarded to Services team for customization work. Regards, Ramya Support Operations
Don't bother -- it's not worth cutting a purchase order for a task that can be done in a few minutes. The support overhead of this request has already cost both companies too much money and time.
We recently moved out from Collabnet's infrastructure