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

Automation uses /rest/api/3/field API endpoint and it's extremely slow

XMLWordPrintable

    • Severity 3 - Minor
    • Jira Service Management

      Issue Summary

      Automation uses /rest/api/3/field API endpoint and it's extremely slow for certain large customers. This slowness is leading to over all execution time of the automation trigger and in turn throttling of service limit(daily processing limit).

      Steps to Reproduce

      1. Setup a simple automation in large tenants(with high number of triggers/automations and issues) with trigger on comment/status change, with conditions to include check of issue type and action to send email/add comment.
      2. You'll notice that it's taking long duration for execution to complete(10sec+)

      Expected Results

      Simple automation triggers should complete execution in less than 3secs

      Actual Results

      Automation is taking long duration for execution to complete(10sec+) and some cases close to 20sec+

      In the automation logs, /rest/api/3/field is taking 3sec just to fetch custom field details/values.

      Workaround

      No workaround at the moment

            [AUTO-778] Automation uses /rest/api/3/field API endpoint and it's extremely slow

            Carol Low made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 943004 ]
            Carol Low made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 918662 ]

            Doug Levitt added a comment -

            FYI - The fix to this issue introduced a regression in Automation for Jira. I can no longer reliably perform general condition checks on fields. I don't understand how Atlassian permitted this.

            See: CES-24908

            As a customer, I cannot invest $$$$ in writing these Automations, only to have Atlassian "change the rules" and break our implementation.

            Doug Levitt added a comment - FYI - The fix to this issue introduced a regression in Automation for Jira. I can no longer reliably perform general condition checks on fields. I don't understand how Atlassian permitted this. See: CES-24908 As a customer, I cannot invest $$$$ in writing these Automations, only to have Atlassian "change the rules" and break our implementation.
            Simmo made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]
            Simmo made changes -
            Status Original: In Progress [ 3 ] New: Waiting for Release [ 12075 ]
            Simmo made changes -
            Status Original: Short Term Backlog [ 12074 ] New: In Progress [ 3 ]

            antonio.freitas added a comment -

            Priority: Medium

            This was changed from high to medium with no context or update it seems. This is affecting very heavily our tenant as explained and forcing us to find alternatives outside of JSM. Can someone please update this?

            antonio.freitas added a comment - Priority: Medium This was changed from high to medium with no context or update it seems. This is affecting very heavily our tenant as explained and forcing us to find alternatives outside of JSM. Can someone please update this?
            James W made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 814620 ]
            Rebecca Smith made changes -
            Priority Original: High [ 2 ] New: Medium [ 3 ]
            Remo Fernandes made changes -
            Priority Original: Medium [ 3 ] New: High [ 2 ]

              Unassigned Unassigned
              b6d0a675f06c Remo Fernandes
              Affected customers:
              3 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: