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

Non-existing user in Administer project permission breaks top dropdown header.

    XMLWordPrintable

Details

    Description

      Summary

      If JIRA has non-existing user in the Administer project permission of the Project Permission then it stops showing top dropdown header.

      Steps to Reproduce

      Use Project Configurator plugin

      1. On Source:
        1. Create a project
        2. Create a user called TestUser1
        3. Amend the permission scheme to use this user, add as admin for project
        4. Export the project config with PC plugin
      2. On Dest
        1. DO NOT CREATE USER TestUser1
        2. Import project config via PC plugin

      Expected Results

      It works fine

      Actual Results

      Top dropdown page header is not present.
      The below exception is thrown in the atlassian-jira.log file:

      2016-04-14 09:51:57,891 http-bio-8443-exec-26 ERROR admin 591x87653x2 1x6uly9 127.0.0.1 /secure/project/ViewProjects.jspa [webwork.util.ValueStack] METHOD: "projectAdmin", exception: 
      com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null!
      	at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:29)
      	at com.atlassian.jira.security.type.SingleUser.hasPermission(SingleUser.java:150)
      	at com.atlassian.jira.security.type.SingleUser.hasPermission(SingleUser.java:138)
      	at com.atlassian.jira.permission.DefaultPermissionSchemeManager$4.hasPermission(DefaultPermissionSchemeManager.java:591)
      	at com.atlassian.jira.permission.DefaultPermissionSchemeManager.hasSchemePermission(DefaultPermissionSchemeManager.java:844)
      	at com.atlassian.jira.permission.DefaultPermissionSchemeManager.hasSchemePermission(DefaultPermissionSchemeManager.java:586)
      	at com.atlassian.jira.security.DefaultPermissionManager.doProjectPermissionCheck(DefaultPermissionManager.java:361)
      	at com.atlassian.jira.security.DefaultPermissionManager.hasPermission(DefaultPermissionManager.java:218)
      	at com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:144)  <+2> (DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:497)
      	at com.atlassian.util.profiling.object.ObjectProfiler.profiledInvoke(ObjectProfiler.java:83)
      	at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:28)
      	at com.sun.proxy.$Proxy14.hasPermission(Unknown Source)
      	at com.atlassian.jira.web.action.project.ViewProjects.isProjectAdmin(ViewProjects.java:98)  <+2> (DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:497)
      	at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70)
      ....
      

      Notes

      Problem may occurs executing other actions, eg: Issue Create.

      Workaround

      • Check project permission page and remove non-existing users
      • Use updated version of Project Configurator plugin. The versions with the fix (1.13.1-J6 and 1.13.1-J7) were released 2016-06-10.

      Attachments

        Activity

          People

            Unassigned Unassigned
            ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: