Queue section in Build Activity dashboard are shown as empty for non-system admin users

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 9.4.0, 9.3.4
    • Affects Version/s: 9.3.2
    • Component/s: Dashboard
    • None
    • 3
    • Severity 3 - Minor

      Issue Summary

      Users are not able to see any queued builds in the Build Activity Dashboard 

      Queue section says "Queue is currently empty" even though users have all the required permissions set on project and plan level whereas System Administrators are able to see queued builds on the dashboard.

       

      This is reproducible on Data Center: (yes)

      Steps to Reproduce

      1. Login to Bamboo version 9.2.3
      2. Create multiple projects and multiple plan link to that.
      3. Create non-admin user which have access to some of the build plans.
      4. upgrade to Bamboo version of 9.3.2.
      5. login to non-admin user and open build activity dashboard.

      Expected Results

      It should show build which are queued under queue section of build activity dashboard.

      Actual Results

      Queue is showing as empty and the illegalargument exception occurred in the atlassian-bamboo.logs.

      2023-09-21 11:18:20,209 ERROR [http-nio-8085-exec-22 url: /bamboo/build/ajax/getDashboardSummary.action; user: user1] [JsonStreamResult]
      java.lang.IllegalArgumentException: null
              at com.google.common.base.Preconditions.checkArgument(Preconditions.java:131) ~[guava-31.0.1-jre.jar:?]
              at com.atlassian.bamboo.utils.ResultKeyUtils.toResultKey(ResultKeyUtils.java:19) ~[atlassian-bamboo-deployments-api-9.3.2.jar:?]
              at com.atlassian.bamboo.ww2.actions.build.QueueItemViewForJsonDecorator.<init>(QueueItemViewForJsonDecorator.java:35) ~[atlassian-bamboo-web-9.3.2.jar:?]
              at com.atlassian.bamboo.ww2.actions.build.BuildQueueItemViewForJsonDecorator.<init>(BuildQueueItemViewForJsonDecorator.java:33) ~[atlassian-bamboo-web-9.3.2.jar:?]
              at com.atlassian.bamboo.ww2.actions.build.AbstractBuildJsonDecorator.<init>(AbstractBuildJsonDecorator.java:49) ~[atlassian-bamboo-web-9.3.2.jar:?]
              at com.atlassian.bamboo.ww2.actions.build.QueuedBuildJsonDecorator.<init>(QueuedBuildJsonDecorator.java:54) ~[atlassian-bamboo-web-9.3.2.jar:?]
              at com.atlassian.bamboo.ww2.actions.build.BuildJsonProviderAction.streamQueuedBuilds(BuildJsonProviderAction.java:160) ~[atlassian-bamboo-web-9.3.2.jar:?]
              at com.atlassian.bamboo.ww2.actions.build.BuildJsonProviderAction.streamJson(BuildJsonProviderAction.java:133) ~[atlassian-bamboo-web-9.3.2.jar:?]
              at com.atlassian.bamboo.ww2.actions.build.DashboardSummaryAction.streamJson(DashboardSummaryAction.java:12) ~[atlassian-bamboo-web-9.3.2.jar:?]
              at com.atlassian.bamboo.struts.JsonStreamResult.execute(JsonStreamResult.java:35) ~[atlassian-bamboo-web-9.3.2.jar:?]
              at com.opensymphony.xwork2.DefaultActionInvocation.executeResult(DefaultActionInvocation.java:375) ~[struts2-core-2.5.30-atlassian-1.jar:2.5.30-atlassian-1]
      

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Alexey Chystoprudov
            Reporter:
            Khushboo Gupta
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: