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.
org.eclipse.core.runtime.CoreException: Unexpected error: com.atlassian.jira.rest.client.RestClientException: java.lang.NullPointerException Product Version = NetBeans IDE 8.0 (Build 201403101706) Operating System = Windows 7 version 6.1 running on amd64 Java; VM; Vendor = 1.8.0 Runtime = Java HotSpot(TM) 64-Bit Server VM 25.0-b70
Created attachment 146458 [details] IDE log
unfortunately, i'm not able to reproduce just by submitting an issue - is there any other info you could provide: - what fields did you change - did you attach any files - does the problem still prevail? - ... thanks
(In reply to Tomas Stupka from comment #2) > unfortunately, i'm not able to reproduce just by submitting an issue - is > there any other info you could provide: > - what fields did you change I selected a component > - did you attach any files No > - does the problem still prevail? Yes, if I select a component. If I don't select any component, the issue can be created. BTW, how do I "unselect" a component in the bug editor once I have selected one?
> BTW, how do I "unselect" a component in the bug editor once I have selected one? ctrl-right-click i guess
(In reply to Tomas Stupka from comment #4) > > BTW, how do I "unselect" a component in the bug editor once I have selected one? > ctrl-right-click i guess OK. thanks BTW, after creating the bug, editing from within Netbeans is extremely limited. - Cancel link in upper right corner does nothing - Status field is empty - Resolution field always shows "Fixed" (regardless of the actual status) and if I change it the change is not submitted - Comments cannot be submitted Maybe because of https://netbeans.org/bugzilla/show_bug.cgi?id=242632 ? Because I get that exception a lot when working with Jira issues
> Maybe because of https://netbeans.org/bugzilla/show_bug.cgi?id=242632 ? yes, could be an after effect of that issue
Does not seem to happen when selecting "JIRA 3.13+" as JIRA connector type in Options -> Team -> Tasks. However, using "JIRA 3.13+" as JIRA connector type may lead to getting blocked on hosted JIRA instances due to "too many requests"
is this reproducible in current dev builds?
one more thing - in case this still happens, could you please try to reload the repository configuration: main menu > find issues > reload attributes (in right bottom corner of the dialog) thanks
*** Bug 243266 has been marked as a duplicate of this bug. ***
any update on this?