Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-72788

Adding a Screen to the Create Issue transition in a workflow will cause the Screens page to go blank

    XMLWordPrintable

Details

    • 8.19
    • 34
    • Severity 3 - Minor
    • 85
    • Hide
      Atlassian Update – 7 October 2021

      Dear Jira users,

      We’re glad to announce that this issue will be addressed in our upcoming 8.20 release.

      Looking forward to your feedback!

      Kind regards,
      Artur Falborski
      Software Engineer, Jira Server and Data Center

      Show
      Atlassian Update – 7 October 2021 Dear Jira users, We’re glad to announce that this issue will be addressed in our upcoming 8.20 release. Looking forward to your feedback! Kind regards, Artur Falborski Software Engineer, Jira Server and Data Center

    Description

      Issue Summary

      When a screen is added to the Create issue transition in Jira, further attempts to navigate under Issues > Screens will result in the page not loading successfully.

      Please note there is a different problem with similar symptoms - JRASERVER-72924.

      Steps to Reproduce

      1. Modify a workflow and add a screen to it under the Create issues transition. The screen you add has to be on the first page of the Issues > Screens page for this to be reproducible.
      2. After publishing the workflow, navigate back to Issues > Screens

      Expected Results

      You can navigate to the page successfully.

      Actual Results

      The following exception is thrown in the atlassian-jira.log file:

      2021-09-02 10:32:52,800-0500 http-nio-48190-exec-23 ERROR admin 632x1647x1 6gzam0 0:0:0:0:0:0:0:1 /rest/api/2/screens [c.a.j.rest.exception.ExceptionInterceptor] Returning internal server error in response
java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker.lambda$_dispatch$0(DispatchProviderHelper.java:181)
    ... 4 filtered
    at com.atlassian.jira.rest.exception.ExceptionInterceptor.intercept(ExceptionInterceptor.java:55)
    ... 1 filtered
    at com.atlassian.jira.rest.v2.issue.scope.RequestScopeInterceptor.intercept(RequestScopeInterceptor.java:39)
    ... 14 filtered
    at com.atlassian.plugins.rest.module.RestDelegatingServletFilter$JerseyOsgiServletContainer.doFilter(RestDelegatingServletFilter.java:160)
    ... 1 filtered
    at com.atlassian.plugins.rest.module.RestDelegatingServletFilter.doFilter(RestDelegatingServletFilter.java:70)
    ... 36 filtered
    at com.atlassian.jira.plugin.mobile.web.filter.MobileAppRequestFilter.doFilter(MobileAppRequestFilter.java:59)
    ... 4 filtered
    at com.atlassian.jira.plugin.mobile.login.MobileLoginSuccessFilter.doFilter(MobileLoginSuccessFilter.java:54)
    ... 3 filtered
    at com.atlassian.diagnostics.internal.platform.monitor.http.HttpRequestMonitoringFilter.doFilter(HttpRequestMonitoringFilter.java:55)
    ... 8 filtered
    at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
    ... 43 filtered
    at com.atlassian.ratelimiting.internal.filter.RateLimitFilter.doFilter(RateLimitFilter.java:73)
    ... 3 filtered
    at com.atlassian.troubleshooting.thready.filter.AbstractThreadNamingFilter.doFilter(AbstractThreadNamingFilter.java:46)
    ... 17 filtered
    at com.atlassian.jira.security.JiraSecurityFilter.lambda$doFilter$0(JiraSecurityFilter.java:66)
    ... 1 filtered
    at com.atlassian.jira.security.JiraSecurityFilter.doFilter(JiraSecurityFilter.java:64)
    ... 16 filtered
    at com.atlassian.plugins.rest.module.servlet.RestSeraphFilter.doFilter(RestSeraphFilter.java:38)
    ... 3 filtered
    at com.atlassian.pats.web.filter.TokenBasedAuthenticationFilter.doFilter(TokenBasedAuthenticationFilter.java:83)
    ... 19 filtered
    at com.atlassian.jira.servermetrics.CorrelationIdPopulatorFilter.doFilter(CorrelationIdPopulatorFilter.java:30)
    ... 5 filtered
    at com.atlassian.plugins.authentication.impl.basicauth.filter.DisableBasicAuthFilter.doFilter(DisableBasicAuthFilter.java:70)
    ... 3 filtered
    at com.atlassian.jwt.internal.servlet.JwtAuthFilter.doFilter(JwtAuthFilter.java:37)
    ... 8 filtered
    at com.atlassian.ratelimiting.internal.filter.RateLimitPreAuthFilter.doFilter(RateLimitPreAuthFilter.java:71)
    ... 3 filtered
    at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
    ... 4 filtered
    at com.atlassian.troubleshooting.thready.filter.AbstractThreadNamingFilter.doFilter(AbstractThreadNamingFilter.java:46)
    ... 3 filtered
    at com.atlassian.web.servlet.plugin.LocationCleanerFilter.doFilter(LocationCleanerFilter.java:36)
    ... 26 filtered
    at com.atlassian.jira.servermetrics.MetricsCollectorFilter.doFilter(MetricsCollectorFilter.java:25)
    ... 25 filtered
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
    at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NumberFormatException: null
    at java.lang.Long.parseLong(Long.java:552)
    at java.lang.Long.valueOf(Long.java:803)
    at com.atlassian.jira.rest.v2.issue.ScreenBean.lambda$expandFieldScreenWorkflows$2(ScreenBean.java:141)
    at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
    at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1556)
    at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
    at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
    at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
    at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
    at com.atlassian.jira.rest.v2.issue.ScreenBean.expandFieldScreenWorkflows(ScreenBean.java:144)
    at com.atlassian.jira.rest.v2.issue.ScreenBean.lambda$new$1(ScreenBean.java:56)
    ... 5 filtered
    at com.atlassian.jira.rest.v2.issue.ScreensResource.lambda$getScreenBeanCrawler$1(ScreensResource.java:551)
    at com.atlassian.jira.rest.v2.issue.ScreensResource.lambda$prepareScreenBeans$3(ScreensResource.java:560)
    at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
    at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
    at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
    at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
    at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
    at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
    at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
    at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
    at com.atlassian.jira.rest.v2.issue.ScreensResource.prepareScreenBeans(ScreensResource.java:563)
    at com.atlassian.jira.rest.v2.issue.ScreensResource.getPaginatedFieldScreens(ScreensResource.java:442)
    at com.atlassian.jira.rest.v2.issue.ScreensResource.getAllScreens(ScreensResource.java:418)
    ... 281 more

      In the UI, you will see the Screens page as blank with an error at the top of the page:

      We couldn't load screens
      We hit a glitch and couldn't complete this operation. Try again.

      Workaround

      • If you navigate under Project settings > Screens, you can still edit the screen in this way.
      • Do not add a Screen that is on the first page of available screens to the Create issue transition within a workflow.

      Attachments

        Issue Links

          is a regression of

          Suggestion - JRASERVER-60894 Add pagination for "Screens" page

          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-72924 Search on View Screens page displays an error if Description is NULL

          • High - High priority issues
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-72852 Loading Screen Admin page fails due to workflows with invalid screen fields

          • High - High priority issues
          • Closed
          is duplicated by

          MNSTR-5521 Loading...

          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Activity

            People

              d996197e70d9 Artur Falborski
              jsanchez2@atlassian.com Jeremy Sanchez
              Votes:
              18 Vote for this issue
              Watchers:
              56 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: