Uploaded image for project: 'Automation for Jira Server'
  1. Automation for Jira Server
  2. JIRAAUTOSERVER-306

Conditions for some fields does not work in Automation for Jira if Jira is installed in the German language

XMLWordPrintable

    • Severity 3 - Minor
    • 0

      Issue Summary

      In Conditions module, Automation for Jira validates using hard coded field names. This causes issues if Jira is installed in German language. As field names to compare are 'hard coded' in English, A4J fails to compare fields if the name of the field is different in German language.

      This behaviour is observed only when Jira is installed in ‘German’ language. If we install Jira in English and change the profile/default language to ‘German’, this issue is not observed.

      Steps to Reproduce

      1. Install Jira in German Language.
      2. Install 'Automation for Jira' plugin.
      3. Configure a rule where "Epic Link" is involved. System field “Epic Link” is called “Epos-Verknüpfung” in German language.
      4. Trigger the rule.

      Expected Results

      Rule should execute successfully as "Epic Exists" will return "true".

      Actual Results

      Rule fails with "No actions performed" as "Epic Exists" will return 'false' even though 'Epic link' is present for the "trigger rule".

      Looks like A4J is looking for “Epic Link” as hardcoded value due to which “Epos-Verknüpfung” value is ignored in "Condition" component of the rule.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

              Unassigned Unassigned
              e8bff493ac7b Karthik Manjunath
              Votes:
              3 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: