nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Send web request 400 error on GET /rest/api/3/issue/{issueIdOrKey}/remotelink

Andy R_mywd7r

Background:
Attempting to use Automation action "Send web request". I am trying to modify https://confluence.atlassian.com/jirakb/how-to-create-and-link-remote-jira-issues-using-automation-1085209850.html to meet my needs. In that KB article, remote issue links are created

I created a Basic auth token in Jira Service Management (free cloud tier).

For a test, I attempted to call api GET /rest/api/3/issue/{issueIdOrKey}/remotelink
https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-remote-links/#api-rest-api-3-issue-issueidorkey-remotelink-get

I added Authorization header with my email/token BASE64 encoded. The response is a 400 error. I can call that api using curl and the same header just fine.

I am testing using the "Validate your web request configuration" option on the "Send web request" page.
The 400 error only says "Bad Request".

Other api calls such as GET /rest/api/3/issue/{issueIdOrKey} do work fine.

Question:

Is this a limitation of the free tier of Jira Service Management? Not being to access GET /rest/api/3/issue/{issueIdOrKey}/remotelink api? Or something else?

Accepted answers

Prince Nyeche - ELFAPP

That means you're sending something the server understands but rejects. What you can do is output the error message for a better understanding of the 400 errors.

All comments

Prince Nyeche - ELFAPP

That means you're sending something the server understands but rejects. What you can do is output the error message for a better understanding of the 400 errors.

Andy R_mywd7r

I am just trying a GET request so there is no body being sent. The GET request url (and Authorization header) from the "Send web request" page in Jira Service Management were copied and run successfully from command line using curl.
The response payload from the Jira "Send web request page" "Validate your web configuration" run is an html page. Script tags removed, the html returned is:

<div class="aui-page-panel">
    <div class="aui-page-panel-inner">
        <section class="aui-page-panel-content">
            <header class="aui-page-header">
                <div class="aui-page-header-inner">
                    <div class="aui-page-header-main"><h1>Bad Request (400)</h1></div><!-- .aui-page-header-main -->
                </div><!-- .aui-page-header-inner --></header><!-- .aui-page-header -->
            <div class="aui-message aui-message-warning warning"><p>Encountered a <code>&quot;400 - Bad
                Request&quot;</code> error while loading this page.</p>
                <p>null</p>
                <p><a href="/secure/MyJiraHome.jspa">Go to Jira home</a></p></div>
        </section><!-- .aui-page-panel-content --> </div><!-- .aui-page-panel-inner --></div><!-- .aui-page-panel -->
</body>

Prince Nyeche - ELFAPP

Do you add the headers as

Authorization Basic Base64encodedString

Authorization Bearer Base64encodedString

However, you say this works for GET issues. Which seems weird, if such errors are there.

Andy R_mywd7r

I have Authorization Basic Base64String as header and it works for GET issues but not when I change the url to remotelink.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-service-desk-cloud

automation

jira-service-management-cloud

jira-service-management