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

Automation does not appear in the list of issue actions when group name include multibyte character

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Medium Medium
    • Trigger - Other
    • None
    • Severity 3 - Minor

      Issue Summary

      Automation rule does not appear in the list of issue actions when group name include multibyte character

      Steps to Reproduce

      1. Create english and Japanese name group (example 'Test' and 'テスト')
      2. Open a issue
      3. Click 'Action' -> 'Create Automation'
      4. Select 'Manual trigger from issue'
      5. Select the 'Test' group on 'Groups that can run trigger' and click Save
      6. Add any component and save the automation rule named 'Rule-1'
      7. Back to the issue and Click 'Action'
      8. You can see the automation rule 'Rule-1'
      9. Back to the automation rule and change group to the 'テスト'
      10. Back to the issue and Click 'Action'
      11. You can't see the automation rule 'Rule-1'.

      Expected Results

      The rule appears in the list even the group name using multibyte character

      Actual Results

      The rule does not appear in the list due to the group name include multibyte character

      Workaround

      Change a group name to without multibyte character

            [AUTO-756] Automation does not appear in the list of issue actions when group name include multibyte character

            Sherry Goyal added a comment -

            Similar to https://jira.atlassian.com/browse/AUTO-694 reported before

            Sherry Goyal added a comment - Similar to https://jira.atlassian.com/browse/AUTO-694 reported before

              Unassigned Unassigned
              6aa6ce5a27d7 K.Kitajima
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: