Loading...

Details

Type: Bug
Resolution: Timed out
Priority: Low
Fix Version/s: None
Affects Version/s: 4.2
Component/s: Issue - Actions
Labels:
Environment:

v4.2-SNAPSHOT#580-r127884, QA-830, HTTPS

Introduced in Version:
4.02
Symptom Severity:
Severity 3 - Minor
Bug Fix Policy:
View Atlassian Server bug fix policy
Current Status:

Hide

Atlassian Update – 16 November 2017

Hi everyone,

The issue has not collected enough votes, watches, comments or support cases during it's lifetime. In this sense overal interest in the reported problem is low.
Jira team is focusing on bigger and more impactful issues at the moment and we are not likely to look at the current bug soon. Therefore I'm resolving the issue as Timed Out.

Atlassian will continue to watch issue for the further updates, so please don't hesitate to share your feedback in the issue comments.

Cheers,
Ignat Alexeyenko
Jira bugmaster.

Show
Atlassian Update – 16 November 2017 Hi everyone, The issue has not collected enough votes, watches, comments or support cases during it's lifetime. In this sense overal interest in the reported problem is low. Jira team is focusing on bigger and more impactful issues at the moment and we are not likely to look at the current bug soon. Therefore I'm resolving the issue as Timed Out . Atlassian will continue to watch issue for the further updates, so please don't hesitate to share your feedback in the issue comments. Cheers, Ignat Alexeyenko Jira bugmaster.

Description

Open up a dashboard with a filter results.
Open one of the issues from filters results in another tab.
Delete the issue from the second tab.
From the original tab click on the issues cog.

You will get a NPE like:

java.lang.NullPointerException
        at com.atlassian.jira.rest.v1.issues.IssueActionsAndOperationsResource.getActionsAndOperations(IssueActionsAndOperationsResource.java:93)
        at com.atlassian.jira.rest.v1.issues.IssueActionsAndOperationsResource.getActionsAndOperationsResponse(IssueActionsAndOperationsResource.java:81)
        at sun.reflect.GeneratedMethodAccessor496.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke(DispatchProviderHelper.java:206)
        at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$1.intercept(DispatchProviderHelper.java:90)
        at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61)
        at com.atlassian.plugins.rest.common.expand.interceptor.ExpandInterceptor.intercept(ExpandInterceptor.java:38)
        at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61)
        at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper.invokeMethodWithInterceptors(DispatchProviderHelper.java:98)
        at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper.access$100(DispatchProviderHelper.java:28)
        at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker._dispatch(DispatchProviderHelper.java:202)
        at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:67)
        at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:163)
        at com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:105)
        at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:111)
        at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:71)
        at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:111)
        at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:63)

From the dashboard UI side you see:

You can do a similar thing on the navigator where you will get:

We should not throw the NPE on the server. For more points, it would be nice if the cog told you that the issue could not be found and that it was likely deleted.

Trying to click the COG menu of an issue that no longer exists causes a NPE on the server

Details

Description

Attachments

Attachments

Activity

People

Dates