The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Error : ERROR Invalid Usage: Post "rest/api/2/search": unsupported protocol scheme ""

Kruthika Hariharan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 7, 2022

Dear Team,



I am trying to create a github action workflow using atlassian/gajira-cli@v3. I am trying to list tickets with a specific summary, for which I am using this 

name: Test-JIRA

on : [workflow_dispatch]  

jobs: Jira-check: 

runs-on: ubuntu-latest

steps: 

- name: setup 

uses: atlassian/gajira-cli@v3 

with: version: 1.0.27  

 - name: Check ticket does not already exist 

id: find 

env: JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }} 

JIRA_USER_EMAIL: ${{ secrets.JIRA_USER_EMAIL }} 

JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }} 

run: jira list --query "resolution=unresolved AND issuetype=Task AND summary~'${{ github.event.pull_request.title }}' AND project=ABC" --queryfields=issuetype,summary,priority,assignee,status,created,reporter,summary

However, I am getting this error ERROR Invalid Usage: Post "rest/api/2/search": unsupported protocol scheme ""Kindly help on this

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
December 7, 2022

Welcome to the Atlassian Community!

That looks like gajira-cli is not including the base URL of the target Jira system in its REST calls.  Have you configured it with the right base URL?

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events