• Type: Bug
• Resolution: Duplicate
• Priority: Medium
• Component/s: Trigger - Other
• Labels:

  None

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

Collapse comment: Sherry Goyal added a comment - 06/Jun/2023 4:00 AM

Sherry Goyal added a comment - 06/Jun/2023 4:00 AM

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

Expand comment: Sherry Goyal added a comment - 06/Jun/2023 4:00 AM

Sherry Goyal added a comment - 06/Jun/2023 4:00 AM Similar to https://jira.atlassian.com/browse/AUTO-694 reported before

Sherry Goyal made changes - 06/Jun/2023 3:58 AM

Resolution		New: Duplicate [ 3 ]
Status	Original: Needs Triage [ 10030 ]	New: Closed [ 6 ]

Sherry Goyal made changes - 06/Jun/2023 3:57 AM

Link

New: This issue duplicates AUTO-694 [ AUTO-694 ]

K.Kitajima made changes - 05/Jun/2023 2:07 AM

Description

Original: h3. Issue Summary Automation rule does not appear in the list of issue actions when group name include multibyte character h3. Steps to Reproduce  # Create english and Japanese name group (example 'Test' and 'テスト')  # Open a issue  # Click 'Action' -> 'Create Automation'  # Select 'Manual trigger from issue'  # Select the 'Test' group on 'Groups that can run trigger' and click Save  # Add any component and save the automation rule named 'Rule-1'  # Back to the issue and Click 'Action'  # You can see the automation rule 'Rule-1'  # Back to the automation rule and change group to the 'テスト'  # Back to the issue and Click 'Action'  # You can't see the automation rule 'Rule-1'. h3. Expected Results The rule appears in the list even the group name using multibyte character h3. Actual Results The rule does not appear in the list due to the group name include multibyte character h3. Workaround Change a group name without multibyte character

New: h3. Issue Summary Automation rule does not appear in the list of issue actions when group name include multibyte character h3. Steps to Reproduce  # Create english and Japanese name group (example 'Test' and 'テスト')  # Open a issue  # Click 'Action' -> 'Create Automation'  # Select 'Manual trigger from issue'  # Select the 'Test' group on 'Groups that can run trigger' and click Save  # Add any component and save the automation rule named 'Rule-1'  # Back to the issue and Click 'Action'  # You can see the automation rule 'Rule-1'  # Back to the automation rule and change group to the 'テスト'  # Back to the issue and Click 'Action'  # You can't see the automation rule 'Rule-1'. h3. Expected Results The rule appears in the list even the group name using multibyte character h3. Actual Results The rule does not appear in the list due to the group name include multibyte character h3. Workaround Change a group name to without multibyte character

K.Kitajima made changes - 05/Jun/2023 2:06 AM

Description

Original: h3. Issue Summary Automation does not appear in the list of issue actions when group name include multibyte character h3. Steps to Reproduce  # Create english and Japanese name group (example 'Test' and 'テスト')  # Open a issue  # Click 'Action' -> 'Create Automation'  # Select 'Manual trigger from issue'  # Select the 'Test' group on 'Groups that can run trigger' and click Save  # Add any component and save the automation rule named 'Rule-1'  # Back to the issue and Click 'Action'  # You can see the automation rule 'Rule-1'  # Back to the automation rule and change group to the 'テスト'  # Back to the issue and Click 'Action'  # You can't see the automation rule 'Rule-1'. h3. Expected Results The rule appears in the list even the group name using multibyte character h3. Actual Results The rule does not appear in the list due to the group name include multibyte character h3. Workaround Change a group name without multibyte character

New: h3. Issue Summary Automation rule does not appear in the list of issue actions when group name include multibyte character h3. Steps to Reproduce  # Create english and Japanese name group (example 'Test' and 'テスト')  # Open a issue  # Click 'Action' -> 'Create Automation'  # Select 'Manual trigger from issue'  # Select the 'Test' group on 'Groups that can run trigger' and click Save  # Add any component and save the automation rule named 'Rule-1'  # Back to the issue and Click 'Action'  # You can see the automation rule 'Rule-1'  # Back to the automation rule and change group to the 'テスト'  # Back to the issue and Click 'Action'  # You can't see the automation rule 'Rule-1'. h3. Expected Results The rule appears in the list even the group name using multibyte character h3. Actual Results The rule does not appear in the list due to the group name include multibyte character h3. Workaround Change a group name without multibyte character

K.Kitajima created issue - 05/Jun/2023 2:05 AM