Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-81160

Automation - Fix Versions Field confusing results when using smart values like 'fieldChange.toString' and 'fieldChange.fromString'

      Summary

      When trying to utilize Jira Automation Rules and Smart Values against the Fix Versions Field, you get strange results.

      These Smart Values work as expected against more simple Fields like 'Description' and 'Summary' but 'Fix Versions' causes unexpected behavior.

      Example Smart Values with unclear results:

      {{fieldChange.fromString}} - Returns the previous value as displayed.{{fieldChange.toString}} - Returns the new value as displayed.
      {{addedFieldChange.values}} - Returns the new value/values added.
      {{deletedFieldChange.values}} - Returns the value/values deleted.

      How to Replicate

      1. Created two new Fix Versions in my Test Site.
      2. Added both of those Fix Versions to my Issue:
      3. Created an Automation Rule which utilizes the Smart Values above.
      4. Expectation is that if you REMOVED both of these Versions from the Issue, that the Audit Log would reflect both of these Fix Versions in the Audit Log.
      5. After navigating back to the issue, select the Fix Versions field to inline edit, select the X to remove both Fix Versions:

        • Result:
      6. The Automation Rule runs, but only writes one of the two removed Fix Versions to the Audit Log:

       

      Expected Results:

      Expectation is that any Fix Versions that are removed from the Issue should be captured and able to be utilized with the 'fieldChange' Smart Values.

      Actual Results:

      Unlike more simple Fields like Description/Summary which are able to print the Smart Values, Fix Versions is not reporting all of the additions and deletes.

       

      Note: I could not find a Component for 'Automation'.

            [JRACLOUD-81160] Automation - Fix Versions Field confusing results when using smart values like 'fieldChange.toString' and 'fieldChange.fromString'

            Please move this automation-related symptom to the AUTO project to improve visibility...

            And as previously noted, this seems to be a duplicate of the known issues with the changelog and list fields such as Fix Versions.

            Thanks!

            Bill Sheboy added a comment - Please move this automation-related symptom to the AUTO project to improve visibility... And as previously noted, this seems to be a duplicate of the known issues with the changelog and list fields such as Fix Versions. Thanks!

            Hello,

            We've been using this smartvalue feature for a while to send emails for auditing purposes but this defect is causing some incorrect reporting.

            Thank you.

            Alex Carson added a comment - Hello, We've been using this smartvalue feature for a while to send emails for auditing purposes but this defect is causing some incorrect reporting. Thank you.

            Moved to long-term backlog as this is a known bug that we do not have capacity to address immediately.

            Alexander Sumer added a comment - Moved to long-term backlog as this is a known bug that we do not have capacity to address immediately.

            This has been a known problem for several years.  Here is the one of the defects created for this for Cloud and Server automation:

            https://jira.atlassian.com/browse/JIRAAUTOSERVER-207

            William Sheboy added a comment - This has been a known problem for several years.  Here is the one of the defects created for this for Cloud and Server automation: https://jira.atlassian.com/browse/JIRAAUTOSERVER-207

              Unassigned Unassigned
              1965e5c0a44d Nathan Phillips
              Affected customers:
              9 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated: