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

Send Web Request action should not deem all 40x responses as problematic

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • Actions
    • 0
    • 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.

    Description

      I'm using Automation For Jira to GET from an external API. 

      If this particular API responds with a 404, that tells me a resource does not (yet) exist, rather than something fatal having occurred.

      Simply ceasing the automation workflow at the point a non-200 response is received is not always desirable. 

      The ability to toggle whether the Web Request action stops or continues after a non-200 response would be most helpful here.

       

      Cheers!

       

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              b5f872756275 Mike Kenyon
              Votes:
              21 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated: