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

Automation rule error message misleading

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Fields
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      Jira Automation is showing a confusing error about the custom fields which are not supposed to be used

      This is reproducible on Data Center: yes

      Steps to Reproduce

      Prerequisites:

      1. Project is using custom fields A, B, C, D, E across its issue types
      2. Issue type XYZ is using custom fields A, B. and not using fields C, D, E

      Steps:

      1. Create an Automation rule with the above project in scope with the following configuration:
        • When: Issue transitioned from status1 to status2
        • If: Issue Type equals: XYZ
        • Then: Create a request
      2. Trigger the automation rule 

      Expected Results:

      The automation rule executes successfully, no errors are shown

      Actual Results

      The automation rule executes successfully, the following error is shown (both in Automation UI and application logs):

      Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -

      C (customfield_XXXXX), D (customfield_XXXXX), E (customfield_18905)

      Workaround

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

              Unassigned Unassigned
              e68278496e06 Alex O
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: