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.

Bug 180843 - NullPointerException at org.netbeans.modules.jira.issue.IssuePanel.allowedStatusTransitions
Summary: NullPointerException at org.netbeans.modules.jira.issue.IssuePanel.allowedSta...
Status: RESOLVED WORKSFORME
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Jira (show other bugs)
Version: 6.x
Hardware: All All
: P4 normal (vote)
Assignee: Jan Stola
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-17 08:15 UTC by weazle
Modified: 2015-02-04 03:21 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 165340


Attachments
stacktrace (1.04 KB, text/plain)
2010-02-17 08:15 UTC, weazle
Details

Note You need to log in before you can comment on or make changes to this bug.
Description weazle 2010-02-17 08:15:48 UTC
Build: NetBeans IDE Dev (Build 201002152000)
VM: Java HotSpot(TM) 64-Bit Server VM, 14.3-b01-101, Java(TM) SE Runtime Environment, 1.6.0_17-b04-248-9M3125
OS: Mac OS X

User Comments:
weazle: 1. Updated Jira Workflow of the current project.
2. changend status on jira server/webform
3. doing a netbenas refresh for the aktual issue => Exception




Stacktrace: 
java.lang.NullPointerException
   at org.netbeans.modules.jira.issue.IssuePanel.allowedStatusTransitions(IssuePanel.java:1048)
   at org.netbeans.modules.jira.issue.IssuePanel.initStatusCombo(IssuePanel.java:267)
   at org.netbeans.modules.jira.issue.IssuePanel.reloadForm(IssuePanel.java:616)
   at org.netbeans.modules.jira.issue.IssuePanel$8.run(IssuePanel.java:958)
   at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
   at java.awt.EventQueue.dispatchEvent(EventQueue.java:633)
Comment 1 weazle 2010-02-17 08:15:53 UTC
Created attachment 94231 [details]
stacktrace
Comment 2 Jan Stola 2010-03-25 14:24:05 UTC
The exception shows that the status passed to IssuePanel.allowedStatusTransitions() is null. AFAIK, this can happen only if JIRA configuration changed (and JIRA repository attributes were not reloaded by the IDE). This is a pretty rare situation => lowering priority.

If you encounter such a situation, you can force attribute/configuration reload by 'Reload Attributes' aciton in Find Issues window (in lower right corner) or in any issue window.

We will try to add some automatic reload if we encounter an unknown status.
Comment 3 Quality Engineering 2015-02-04 03:21:22 UTC
Reported for 7.3.x or earlier, no new info since then -> closing as worksforme, please reopen in case you see it.