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.
Summary: | Can not report new issue on Kenai project | ||
---|---|---|---|
Product: | connecteddeveloper | Reporter: | hantsy <hantsy> |
Component: | Issuetracking Framework | Assignee: | Tomas Stupka <tstupka> |
Status: | NEW --- | ||
Severity: | blocker | ||
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
screenshot
screenshot |
Description
hantsy
2009-10-24 10:43:11 UTC
Created attachment 90043 [details]
screenshot
the item "NetBeans Extesion Collections" was created by netbeans to represent your kenai project the "nbx" item must have been created by you in the services widow - why did you do that? the other item should be enough to work with your jira project wasn't able to reproduce so some additional info could be usefull - what url did you use for the "nbx" repository? - could you, please, reproduce the problem, create a thread dump and attach it to this issue? - attach also your messages.log file after reproducing the problem thanks I do not remember if the "nbx" node in service is created by myself... I only want to test the issue tracker connection in the service windows...but it seem it does not work correctly. May be this can not reproduce now. The nbx project is migrated to jira now. right click on the "nbx" node in the services tab and choose "Edit..." - i'd like to know what the url is. Created attachment 90162 [details]
screenshot
caused by the url - http://kenai.com/bugzilla/buglist.cgi?product=nbx&order=Impotance&limit=25 1.) its invalid now as the project is racked by jira now 2.) even if bugzilla would be still active the format should be "http://kenai.com/bugzilla" no configuration is returned if trying with the url above - we should handle it properly even if the url is invalid wrong user setup and corner case => p4 If the kenai.com issue tracker is changed, it maybe provide some approaches to notice user and refresh the related nodes and combox values. Maybe this bug is related to 175446 Kenai.com cannot notify us about this change - what happened: You created an issue tracker pointing to some URL and then you made this URL invalid by changing the type of an issue tracker... Kenai was not involved in any way in the problem. But I think NetBeans can "pull" the information from Kenai.com when connection failed by before local configuration, then notice you the result. It is no need Kenai.com push result to NetBeans IDE. Yes, if the issue tracker is not available, we could show the dialog... |