Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-694

Manual Automation rule will not list in dropdown if we restrict the rule group can run and if group name is non-English or Its with automated trigger as well where project deafult langue is german its not passing the condition for service desk team role

    • Minor

      Issue Summary

      Issue 1: The Manual Automation rule will not list in the dropdown if we restrict the rule to a certain group that can run only and the group name is non-English such as German, or Japanese.

      Issue 2:  If the project's default language is German, when I run an automation, it does not get passed if the condition is User who triggered the event service desk team role. 

      Steps to Reproduce

      Issue 1

      1. Create a German group with a name ex. Kühne IT in admin.atlassian.com
      2. Create an automation rule and the trigger should be manual.
      3. Restrict the rule can run only people of this group Kühne IT .
      4. Go to any issue and try to find this rule, you will be unable to see this rule in the dropdown.
      5. I would like to attach here the Screen Recording 2023-03-20 at 13.28.24_compressed.mp4 of the whole symptom. 

      Issue 2

      • Set Jira Site Language to German:
        • Navigate to Jira settings.
        • Change the site language preference to German.
      • Create Service Desk Project in German:
        • Initiate the creation of a new service desk project.
        • Ensure the default language for the project is set to German.
      • Set Up Automation Rule:
        • Define a new automation rule in Jira.
        • Condition: User triggering the event must belong to the "Service Desk Team" role.

      Expected Results

      The rule should be visible regardless to run.

      Actual Results

      No exception simply rule is not visible to run.

      ...
      

      Workaround

      if there is no workaround please state: NA

            [AUTO-694] Manual Automation rule will not list in dropdown if we restrict the rule group can run and if group name is non-English or Its with automated trigger as well where project deafult langue is german its not passing the condition for service desk team role

            T. Vanessa added a comment -

            Hello,

            Same problem in French with some caracters like é, è, à, ù, ç.

            Contourn solution is rename group without special caracter

            T. Vanessa added a comment - Hello, Same problem in French with some caracters like é, è, à, ù, ç. Contourn solution is rename group without special caracter

            Robin added a comment -

            The group name can be any language, as long as it uses only ascii chars. There seems to be a lack of Unicode support in handling the conditional access by group for manually starting automation rules.

            Robin added a comment - The group name can be any language, as long as it uses only ascii chars. There seems to be a lack of Unicode support in handling the conditional access by group for manually starting automation rules.

            NiYunfan added a comment -

            Chinese group name also failed

            NiYunfan added a comment - Chinese group name also failed

            Robin added a comment -

            Hi,

            I am the person who originally reported this to support, let me add the following details:

            German language contains some special characters (ü,ä,ö,ß). If there are groups with any of those characters in their name listed inside the "who can run this rule" condition for a rule with a manual trigger, the users in these groups don't see the option to execute the rule inside any issue. Changing the group name resolves the issue and can be used as workaround.

            Best regards,

            Robin

            Robin added a comment - Hi, I am the person who originally reported this to support, let me add the following details: German language contains some special characters (ü,ä,ö,ß). If there are groups with any of those characters in their name listed inside the "who can run this rule" condition for a rule with a manual trigger, the users in these groups don't see the option to execute the rule inside any issue. Changing the group name resolves the issue and can be used as workaround. Best regards, Robin

              dfc44bd03767 Scott Bell
              61315266b1bc Deepak Rai
              Affected customers:
              8 This affects my team
              Watchers:
              14 Start watching this issue

                Created:
                Updated: