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

Filters throw exception, if one of the LDAP groups is renamed

    XMLWordPrintable

Details

    • 4
    • 1
    • Severity 3 - Minor
    • 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

      Renaming a group in LDAP, leads to the following exception in filters, as the expected group cannot be found:

      2009-10-16 07:01:54,069 http-80-Processor18 ERROR [velocity] Method getCountsForFilter threw exception for reference $portlet in template templates/plugins/jira/portlets/savedfilters.vm at [26,42]
      2009-10-16 07:01:54,069 http-80-Processor18 ERROR [com.atlassian.velocity.DefaultVelocityManager] MethodInvocationException occurred getting message body from Velocity: java.lang.IllegalArgumentException: No group 'SG - AWSEIT Admin' found.
      java.lang.IllegalArgumentException: No group 'SG - AWSEIT Admin' found.
      at com.atlassian.jira.security.roles.actor.GroupRoleActorFactory$GroupRoleActor.getGroup(GroupRoleActorFactory.java:109)
      at com.atlassian.jira.security.roles.actor.GroupRoleActorFactory$GroupRoleActor.contains(GroupRoleActorFactory.java:88)
      at com.atlassian.jira.security.roles.CachingProjectRoleAndActorStore$CachedDefaultRoleActors.contains(CachingProjectRoleAndActorStore.java:476)

      A more user-friendly message indicating the cause would be helpful.

      As a workaround, re-create the filter or revert back the changes made to the LDAP group name.

      Attachments

        Issue Links

          is incorporated by

          Suggestion - JRASERVER-1962 Improve the LDAP stack in JIRA

          • Closed

          Activity

            People

              Unassigned Unassigned
              ganand Gurleen Anand [Atlassian]
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: